October 6th, 2014 - SQL Compare 11 is now available for download from the Red Gate website.
Support for SQL Server 2014 object types
You can use SQL Compare 11 to compare and deploy:
• memory-optimized tables
• natively compiled stored procedures
• memory-optimized table types (When you deploy a database containing memory-optimized objects (memory-optimized tables, natively compiled stored procedures and memory-optimized table types), we recommend you perform two deployments. See Deploying memory-optimized objects.)
• clustered columnstore indexes
• incremental statistics (If the ‘Ignore filegroups, partition schemes and partition functions’ project option is selected, the deployment of incremental statistics might fail if they rely on partition schemes or functions which are being ignored.)
Backup commands in the deployment script
When you select the 'Back up before deployment' option in the deployment wizard, the backup commands are now included in the deployment script. This means you can now back up the target when you create a deployment script to run in Management Studio.
SQL Compare 11 no longer supports SQL Backup Standard or SQL Backup Lite.
‘Do not add error handling statements to deployment scripts’ project option
When you run the deployment script in Management Studio, this option allows the deployment script to fail when an error is encountered. You can only select this option if transactions aren't used in deployment scripts. When you deploy directly from SQL Compare, the deployment is always terminated when an error is encountered.
Breaking change to Ignore WITH NOCHECK option
If your existing SQL Compare projects use the Ignore WITH NOCHECK option (or if your command line arguments use IgnoreWithNoCheck), you may get unexpected results when you use them with SQL Compare 11.
In previous versions of SQL Compare, the Ignore WITH NOCHECK option ignored both the NOCHECK and WITH NOCHECK arguments on foreign keys and check constraints. In SQL Compare 11, Ignore WITH NOCHECK doesn't ignore the NOCHECK argument. If you want your projects to continue ignoring both NOCHECK and WITH NOCHECK arguments, you must select the new option Ignore NOCHECK and WITH NOCHECK (or specify the command line option IgnoreNoCheckAndWithNoCheck).
• SC-5662: Clicking Owner Mapping tab followed by Table Mapping tab no longer incorrectly shows “No data source selected” when data sources have been set up
• SC-5853: System.OverflowException is no longer thrown for large values of syscolumns.columnID associated with table columns
• SC-6051: Partitioned tables no longer rebuild when the number of partitions of the underlying partition schemes change
• SC-6263: Serializing/deserializing partition functions with null values no longer causes NullReferenceException
• SC-6438: (Regression) Registering partition functions with null values no longer throws an error
• SC-6632: ALTER SCHEMA statement is now included for objects whose name has not changed but schema has
• SC-6650: When using /include="StaticData" and a static data table's primary key consists of a field that is a user-defined table, comparison no longer fails with "Unsupported column type - Empty"
• SC-6750: A table rebuild is no longer incorrectly scripted out when deploying changes in tables with FILESTREAM columns
• SC-6875: Fix for the issue where inconsistent comparison results are shown when reversing compare direction between scripts folder and database for compressed partitioned tables
• SC-6985: TesselationScheme is now correctly registered on spatial indexes
• SC-7319: Adding dependencies for certain CLR in backups no longer causes NullReferenceException
• SC-7370: Sequences no longer show differences when they are equal
• SC-7399: ALTER INDEX REBUILD statements in scripts folder are now parsed
• SC-7424: Columstore indexes are now scripted out regardless of the target database’s compatibility mode
• SC-7451: Fix for the issue where ANSI_NULLS is reported incorrectly in SQL Server 2005 and 2008 after certain ALTER VIEW operations
• SC-7464: A duplicate extended property name when registering user-defined table type