In our enviroment we host data for multiple clients, each client having a seperate database. The schema should be the same across all of these databases, except for the DATA_COMPRESSION on some of the databases where this has been customised for the volume of data actually stored in the table.
When attempting to deploy via VS2010 or vsdbcmd to those database where the DATA_COMPRESSION is row or page, the generated script rebuilds the table without compression.
Is there anyway to tell the deployment engine to not check the DATA_COMPRESSION setting?
Jeremy HartleyWednesday, October 13, 2010 11:26 AM
Did the reply from Gert solve your problem? I am having this problem too, and it looks similar to this Connect bug: https://connect.microsoft.com/VisualStudio/feedback/details/552756/cant-get-schema-compare-to-ignore-data-compression-table-option?wa=wsignin1.0 Would you agree?
DavidMonday, October 18, 2010 10:48 PM