Fulltext Indext Stoplist Options

Compares and synchronizes SQL Server databases, backups and scripts.

Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong

Fulltext Indext Stoplist Options

Postby howarthcd » Mon May 20, 2013 3:05 pm

When comparing a table script file containing a full text index definition with another script file with an equivalent fulltext definition but where the STOPLIST option is included, then SQL Compare treats the scripts as being the same even though the differencing pane highlights the differences between the scripts.

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
howarthcd
 
Posts: 50
Joined: Wed May 16, 2007 10:30 am

Postby stanori » Wed May 22, 2013 8:18 pm

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
_________________
Steve Tanori
Product Support
Red Gate Software Ltd.
866-997-0378
stanori
 
Posts: 84
Joined: Mon Apr 23, 2012 1:13 pm

Postby howarthcd » Wed May 22, 2013 9:03 pm

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
howarthcd
 
Posts: 50
Joined: Wed May 16, 2007 10:30 am


Return to SQL Compare 10

Who is online

Users browsing this forum: No registered users and 1 guest