Comments
2 comments
-
Hi howarthcd,
Thanks for your post regarding SQL Compare. Unfortunately, there is not a way to present this difference at the same object level as a table. SQL Compare treats this difference at the table level, and will generate the appropriate change in the resulting deployment script.
I would suggest posting your feature request in the following forum so that others can vote as well:
http://redgate.uservoice.com/forums/141 ... uggestions
Best Regards,
Steve -
Hi Steve
Thanks for your reply, however this isn't a feature request - I believe that it is a bug.
The point is that although the fulltext index definition differs there is no relevant sync statement included in the synchronisation script.
Chris
Add comment
Please sign in to leave a comment.
e.g.
1st script contains this:
CREATE FULLTEXT INDEX ON [dbo].[MyTable] KEY INDEX [PK_MyTable] ON [ftCatalog] WITH STOPLIST OFF
GO
2nd script contains this:
CREATE FULLTEXT INDEX ON [dbo].[MyTable] KEY INDEX [PK_MyTable] ON [ftCatalog]
GO
Is there a project option that can be specified so that this difference is raised at the table level? Full-text indexing is not selected under the 'Ignore' project option.
SQL Compare 10.3.8.406 Professional Edition running on Windows 7 64-bit.
Thanks
Chris