11.2.9 - August 17th, 2015

FREQUENT UPDATES RELEASE

New Features

Improved support for comparing and deploying Azure v12 databases. The following features are now supported for Azure v12:

• CLR assemblies
• Deploying stored procedures and user defined functions WITH ENCRYPTION
• INTO and OVER clauses in SELECT statements
• Newly supported index options
• Newly supported trigger options
• ROWGUIDCOL
• Stored procedures FOR REPLICATION
• User defined types (CREATE TYPE)
• XML columns and types
• XML Schema Collections
• SC-8003: SQL Compare no longer incorrectly warns that selective XML indexes are unsupported in Azure v12

 Bug Fixes

• SC-4544: The /help documentation for the /project command line option now correctly states that you cannot use it in conjunction with the /include or /exclude switches.
• SC-7653: SQL Compare now correctly reads non-ASCII characters from script folders with Windows Code Page 1252 or UTF-8 (without preamble) character encodings

 Known Issues

• SQL Compare cannot decrypt encrypted stored procedures and functions from Azure SQL Databases.
• While SQL Compare can now compare and deploy partition functions and schemes to Azure v12 databases, it does not currently apply partition schemes to tables. If you wish to deploy partitioned tables, you will need to manually edit the deployment script to add the appropriate ON <partition_scheme> syntax. This bug (SC-8012) will be fixed in a future release.

11.2.8 - August 10th, 2015

 FREQUENT UPDATES RELEASE

Features

Improved support for registering and deploying to Azure V12 databases, including support for the following object types:

• Full text stop lists
• Extended properties
• Defaults
• Sequences
• XML indexes

Fixes

• SC-7993: Full text search is now correctly identified as being enabled on a Azure V12 databases

• SC-7997: Non-breaking spaces in stored procedure definitions are now parsed correctly as whitespace

• SC-7923: User-defined functions that override system functions can now be registered from scripts folders

• SC-7991: Databases with spaces in their name can now be registered from SQL Server 2000

• SC-8001: Databases with ‘{’ and ‘}’ characters in their name can now be registered

• SC-7996: Improved performance of registering foreign keys from live databases

• SC-7793: Selective XML indexes are now registered from Azure V12 databases

Known issues

• Index options that were unsupported in Azure V11 are not currently registered from Azure V12. (eg ALLOW_ROW_LOCKS)
• SQL Compare may incorrectly warn that selective XML indexes are not supported when deploying to Azure SQL Database V12. SQL Compare will still allow you to deploy the selective XML indexes, and you can safely ignore the warning

11.2.7 - August 3rd, 2015

FREQUENT UPDATES RELEASE

Fixes

• SC-4997: Azure V11 and V12 have been added to the list of SQL Server versions in the 'comparison settings for scripts folder'. This means that SQL Compare can now handle Azure scripts folders correctly
• SC-7222: Roles are now dropped before users, so that SQL Compare can successfully drop a user that owns a role
• SC-7853: SQL Compare no longer unnecessarily tries to decrypt database objects that are not actually encrypted. This should significantly improve the speed of comparisons with databases that only have a few encrypted objects
• SC-7160: TRY_CAST, CAST, or TRY_CONVERT function calls in computed column expressions are no longer incorrectly changed to CONVERT calls
• SC-7910: SQL Compare now correctly recognises and deploys full text catalogs and indexes in Azure SQL Database V12 instances
• SC-7929: SQL Compare no longer generates invalid syntax for spatial index BOUNDING_BOX definitions when Windows regional settings are set to a locale that uses commas as decimal separators (e.g. German language settings)
• SC-7934: SQL Compare now correctly identifies changes in foreign key column ordering as differences
• SC-7936: User names containing apostrophe characters (') are now correctly escaped in calls to sp_droprolemember
• SC-7961: SQL Compare no longer incorrectly adds a schema prefix to the index name in index definitions within stored procedures when mapping across schemas
• SC-7962: SQL Compare no longer incorrectly adds a schema prefix to DELETED/INSERTED output clauses within stored procedures when mapping across schemas

Known Issues

• SQL Compare may incorrectly warn that full text search is not enabled when deploying full-text catalogs/indexes to an Azure SQL Database V12. SQL Compare will still allow you to deploy the full-text objects, and you can safely ignore the warning.

11.2.6 - July 22nd, 2015

FREQUENT UPDATES RELEASE

Fixes

• SQL Compare no longer produces incorrect warnings about NOT FOR REPLICATION being unsupported in SQL Server 2005 and later
• More reliable detection of SQL Server compatibility level

11.2.5 - July 16th, 2015

FREQUENT UPDATES RELEASE

Features

Azure v12 improvements

Initial support for Azure v12 features:

• CLR features: CLR Assemblies, along with CLR user-defined types, triggers, functions, and stored procedures
• XML schema collections and XML data types
• sequence objects
• columnstore indexes

Limitations of Azure support

We’re still ironing out the details of what Azure v12 does and doesn't support compared with SQL Server. If you find any bugs, please get in touch.

11.2.3 - June 10th, 2015

FREQUENT UPDATES RELEASE

Features

Azure v12 and SQL Server 2016 connectivity

SQL Compare can now connect to Azure v12 and SQL Server 2016 CTP2 instances. Full support for new SQL Server features will be coming in the future.

11.2.2 - June 3rd, 2015

FREQUENT UPDATES RELEASE

Features

64-bit support

SQL Compare will now run as a 64-bit process on a 64-bit OS. This applies to both the main application GUI  and the SQLCompare.exe command-line.

Fixes

• SC-7873: When the "ignore SET QUOTED_IDENTIFIER and SET ANSI_NULLS statements" option is enabled, SQL Compare will now correctly ignore those statements within stored procedures 
  

11.2.1 - May 27th, 2015

Fixes

• SC-5151: XML schema collections that have additional child nodes in the target database are now correctly detected as different
• SC-5533: Permission changes for system users (e.g. 'guest') are now correctly ignored when the "ignore users’ permissions and role memberships” option is selected
• SC-6447: The command line now correctly honours filters when using the /project argument to specify a project file. This applies to filters stored within the project file and also to filters loaded via the /filter argument
• SC-7896: When a service's queue changes, the deployment script no longer contains a duplicate ALTER SERVICE statement
• SC-7897: Square brackets in user names are now correctly escaped in a DROP USER statement
• SC-7898: Square brackets in constraint names are now correctly escaped in an ALTER TABLE [tbl] NOCHECK CONSTRAINT statement
• SC-7900: Square brackets in user names are now correctly escaped in an ALTER AUTHORIZATION ON ASSEMBLY statement
• SC-7901: Square brackets in catalog names are now correctly escaped in a CREATE FULLTEXT CATALOG statement
• SC-7903: Square brackets in user names are now correctly escaped in the AUTHORIZATION part of a CREATE FULLTEXT CATALOG statement
• SC-7907: Square brackets in user defined type names are now correctly escaped in CREATE TABLE column definitions

• SELECT statements containing a 'WITH (SNAPSHOT)' query hint no longer cause a parsing error

11.2.0 - May 7th, 2015 

Note: Version 11.2 rolls up all of the changes from frequent update versions 11.1.4 to 11.2.0 - if you want to receive these kinds of updates more quickly in future, you should turn on Frequent Updates.

Features

New for 11.2

• Filter rules can now use two new match operators, LIKE and NOT LIKE, in addition to the existing operators. These support the standard T-SQL LIKE syntax for wildcard characters ('%', '_', '[abc]', and '[^abc]' - see MSDN for details). The other match operators will no longer treat those characters as special wildcard characters.

From previous 11.1.x frequent updates

• Project options are now listed in alphabetical order.
• Unique constraints on a table are now created immediately after the table in deployment scripts.
• Full-text catalogs are created before transactions begin in deployment scripts.
• SC-7710: SQL Compare will now recognise and deploy selective XML indexes.
• The default value for the /BackupProvider switch on the command line is now Native, instead of SQB.

Fixes

New for 11.2

• SC-5346: Attempting to configure a filter rule with a single-quote character (') in its value no longer causes an error.

• SC-5894: Underscore (_) and percent (%) characters in begins with, ends with, and contains filters are no longer treated as wildcards. This means that, for example, using a filter to exclude object names beginning with '_' no longer causes all objects to be excluded.

• SC-7219, SC-7578: the keywords DIFFERENTIAL, READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, and SNAPSHOT are now correctly highlighted as keywords in the deployment script

• SC-7811: Using the 'Create database...' option when configuring the target database no longer causes an error when the source database name is empty

• SC-7872: Square brackets in constraint names are now correctly escaped in the deployment script when the constraint is being dropped

From previous 11.1.x frequent updates

• SC-1196: Full-text indexes are now deployed before stored procedures when the "do not use transactions in deployment scripts" option is turned on, which fixes an issue where deployment of a full-text index and a stored procedure depending on that index would fail.
• SC-7845: Snapshots created from live databases no longer contain system services.
• SC-7837: SQL Compare no longer hangs when trying to read a scripts folder containing invalid T-SQL files. This fix also means that when logging is turned on, Compare no longer produces excessively large log files in this situation.
• SC-5561: SQL Compare will trim file names generated for deployment scripts if they would exceed the maximum Windows path length.
• SC-7497: Using multiple options in a SET STATISTICS statement (e.g. SET STATISTICS TIME, IO ON) in a scripts folder no longer causes an error.
• SC-7621, SC-7632: System functions are no longer incorrectly treated as objects in deployment scripts.
• SC-7750: Using the <Create Database...> command no longer causes an error when the other side of the comparison is a backup, snapshot or source control repository.
• SC-7768: SQL errors during deployment now give more detailed messages.
• SC-7820: Using the optional '=' in the SET STOPLIST part of an ALTER FULLTEXT INDEX statement in a scripts folder no longer causes an error.
• SC-4542: SQL Compare should now refresh views less often; it will no longer refresh views unrelated to the deployment and will refresh no views if the 'Include Dependencies' option is disabled
• SC-7788: SQL Compare will now generate a correct existence check for certain triggers when the 'Add object existence checks' option is enabled.
• SC-7766: SQL Compare will no longer crash when refreshing a comparison containing a user-defined table type that references an XML schema collection.

• SC-7587: Deploying to a scripts folder with the "Do not use transactions" option enabled no longer warns about transactions being disabled

• SC-7645: Deployment scripts generated using the command line with a project file now contain the database name

• SC-7707: Constraints are no longer dropped incorrectly when an index is changed and the ‘ignore constraint names’ option is enabled

• SC-7757: When the 'Add object existence checks' option is enabled, generating a deployment script will no longer raise an error if a foreign key will be dropped

• SC-6280, SC-7739: Scripts folders containing partition function definitions that use non-integer partition values no longer cause an error during comparison
• SC-7342: Partition functions that differ only in precision and/or scale are now correctly detected as different
• SC-7552: SQL Compare no longer generates invalid null characters (&#x0;) in XML reports for comparisons that involve database extended properties
• SC-7718: When the 'Add object existence checks' option is enabled, existence checks are now correctly generated when altering constraint definitions
• SC-7719: When the 'use case sensitive object definition' option is disabled, tables that differ only in the casing of their schema names are no longer reported as different
• SC-7733: When the 'Add object existence checks' option is enabled, the correct 'IF EXISTS' check is now used when altering a function
• SC-7741: Differences in DATA_COMPRESSION mode in indexes on views are now correctly detected when comparing against scripts folders

Known issues

Upgrading filters from versions 11.1 and earlier

The filter changes in this release mean that if you have an existing filter rule that contains an opening square bracket ([ character), the filter will behave differently in this version. The filter operator will change to LIKE or NOT LIKE, and the square brackets will be treated as they would be in a T-SQL LIKE match. To make your filter behave as it did before, you will need to edit the affected filter rules, either by changing the operator to begins with, ends with, or contains, or by escaping the opening square bracket as '[[]'.