SQL Packager 6

Invalid SQL when synchronizing an index to a scripts folder when data compression is specified

When attempting to synchronize a database to a scripts folder in SQL Compare, some existing SQL code in the scripts folder may cause SQL Compare to show a warning regarding invalid SQL. If this happens because an index specifies SQL Server 2008 data compression, this is a known issue in SQL Compare. For example, the following syntax will be flagged as invalid:

ALTER TABLE [dbo].[MyTable] ADD CONSTRAINT [PK_MyTable] PRIMARY KEY CLUSTERED ([MyColumn]) WITH (DATA_COMPRESSION = PAGE)

The warning message can be safely ignored, however the table will always be flagged as "different", even after synchronization because the invalid syntax warning will always cause SQL Compare to err on the side of caution and flag the object as different. We are aware of this and our engineers are going to fix it in a future version.

If you continue to experience problems, please contact Red Gate Support.


Didn't find what you were looking for?