SQL Compare beta v11.0.0.184 is now available
JonathanWatts
Posts: 418
We've now released the fourth beta of SQL Compare 11 (11.0.0.184), which you can download from the Red Gate website.
The full release notes for all versions of SQL Compare v11 are available in this thread.
Features for this version:
This version includes support for memory-optimized tables. SQL Compare can now:
• perform a deployment to create, drop and rebuild memory-optimized tables on SQL Server 2014 databases
• drop and recreate database level event notifications for CREATE TABLE and DROP TABLE statements when memory-optimized tables are deployed
If your deployment includes memory-optimized tables, you need to:
• make sure that the target database has a memory-optimized filegroup
• turn on the ‘Do not use transactions in deployment scripts’ option
Behavioral differences
• If you turn on the ‘Ignore indexes’ option, differences in indexes for memory-optimized tables are ignored if the only differences between the tables are the indexes. However, if there are other differences between the tables, all indexes will be deployed.
• The ‘Ignore collations’ option is not applied to memory-optimized tables.
Known issues and further improvements
We're currently working on adding support for:
• deploying memory-optimized tables from a SQL Server 2014 database to a database on an older version of SQL Server
• dropping and recreating database level triggers for CREATE TABLE and DROP TABLE statements on a target database when memory-optimized tables are deployed
• deployment using transactions for other objects types when they're deployed alongside memory-optimized tables. For example, if you deploy functions alongside memory-optimized tables, there will be no transaction block for the section in the deployment script for deploying the functions
• other new features in SQL Server 2014 including memory-optimized table types, natively compiled stored procedures, clustered columnstore indexes and incremental statistics. This latest SQL Compare beta may display incorrect SQL for these objects, and attempts to deploy them are likely to fail or result in incorrect deployment
N.B. SQL Compare 11 won't include support for comparing and deploying backup files (native or SQL Backup) containing memory-optimized tables.
Bug fixes
This version includes the following bug fixes:
• SC-7260: Fillfactor option no longer appears in user-defined table types
• SC-5164: Fix for the issue where SQL Compare attempts to re-add extended properties when altering a function with existing extended properties
• SC-7248: Assemblies with circular dependencies on other assemblies no longer causes stackoverflow exception
• SC-5443: Using drop and create instead of alter option no longer throws an error after dropping a view then trying to refresh it
• SC-7142: Migration scripts are now retrieved by command line
• SC-6835: *= operator in stored procedures is now properly parsed
• SC-7063: A TIMEOUT value of -1 when retrieving messages from a queue no longer causes parsing error
Thanks,
The SQL Compare team
The full release notes for all versions of SQL Compare v11 are available in this thread.
Features for this version:
This version includes support for memory-optimized tables. SQL Compare can now:
• perform a deployment to create, drop and rebuild memory-optimized tables on SQL Server 2014 databases
• drop and recreate database level event notifications for CREATE TABLE and DROP TABLE statements when memory-optimized tables are deployed
If your deployment includes memory-optimized tables, you need to:
• make sure that the target database has a memory-optimized filegroup
• turn on the ‘Do not use transactions in deployment scripts’ option
Behavioral differences
• If you turn on the ‘Ignore indexes’ option, differences in indexes for memory-optimized tables are ignored if the only differences between the tables are the indexes. However, if there are other differences between the tables, all indexes will be deployed.
• The ‘Ignore collations’ option is not applied to memory-optimized tables.
Known issues and further improvements
We're currently working on adding support for:
• deploying memory-optimized tables from a SQL Server 2014 database to a database on an older version of SQL Server
• dropping and recreating database level triggers for CREATE TABLE and DROP TABLE statements on a target database when memory-optimized tables are deployed
• deployment using transactions for other objects types when they're deployed alongside memory-optimized tables. For example, if you deploy functions alongside memory-optimized tables, there will be no transaction block for the section in the deployment script for deploying the functions
• other new features in SQL Server 2014 including memory-optimized table types, natively compiled stored procedures, clustered columnstore indexes and incremental statistics. This latest SQL Compare beta may display incorrect SQL for these objects, and attempts to deploy them are likely to fail or result in incorrect deployment
N.B. SQL Compare 11 won't include support for comparing and deploying backup files (native or SQL Backup) containing memory-optimized tables.
Bug fixes
This version includes the following bug fixes:
• SC-7260: Fillfactor option no longer appears in user-defined table types
• SC-5164: Fix for the issue where SQL Compare attempts to re-add extended properties when altering a function with existing extended properties
• SC-7248: Assemblies with circular dependencies on other assemblies no longer causes stackoverflow exception
• SC-5443: Using drop and create instead of alter option no longer throws an error after dropping a view then trying to refresh it
• SC-7142: Migration scripts are now retrieved by command line
• SC-6835: *= operator in stored procedures is now properly parsed
• SC-7063: A TIMEOUT value of -1 when retrieving messages from a queue no longer causes parsing error
Thanks,
The SQL Compare team
Jonathan Watts
-Project Manager
-Red Gate Software Ltd
-Project Manager
-Red Gate Software Ltd