Comparison gaffe with data compression

Forum for users of SQL Compare schema synchronization utility

Comparison gaffe with data compression

Postby AaronBertrand » Mon Jul 12, 2010 2:16 pm

I am comparing two 2008 databases with a page compressed index. If there are any major differences between the two tables (e.g. a foreign key is missing from one side), the comparison shows that I also need to add COMPRESSION = PAGE to one of the tables. The resulting script shows nothing about this however, and if I create the foreign key manually (not changing anything with compression), the tables are now considered identical. See screen shot below for the comparison delta indicator and the resulting script (which also changes nothing about compression).

Posts: 44
Joined: Wed Oct 22, 2008 12:26 pm

Postby Chris Auckland » Mon Mar 19, 2012 7:52 pm

This has now been fixed in SQL Compare 10.1 and can be downloaded through Help | 'Check for Updates'
Chris Auckland
Posts: 760
Joined: Tue Oct 24, 2006 1:12 pm
Location: Red Gate Software Ltd.

Return to SQL Compare Previous Versions

Who is online

Users browsing this forum: Google [Bot] and 1 guest