Page History

This build includes many new features and fixed issues, including the following updates from previous releases.

4.1 New features

Windows .NET 4.0 support

• SQL Comparison Toolset 4.1 supports all Microsoft Windows operating systems using .NET 4.0.

SQL Schema Compare

• Enhanced user interface. SQL Schema Compare includes a new ribbon control that improves the usability of the tool.
• Entity filter replace schema filters. Entity filters replace schema filters used to filter data. In the user interface, you can access these filters from the context menu of the comparison grid. The command line interface includes three additional sample xml files that provide additional information about how to use the entity filters. For more information about using these filters, see the online help accessible from within SQL Comparison Toolset.

4.1 Fixed Issues

• This release removes a table dependency that negatively affected performance for some users with large databases.
• This release fixes a table scripting issue with the TEXTIMAGE_ON clause. SQL Server requires the TEXTIMAGE_ON clause when a table contains large binary fields, such as image, text, and ntext. This issue caused the SQL Server system catalog to become out-of-date and fail to report the clause properly. SQL Comparison Toolset 4.1 contains additional checks and scripts the TEXTIMAGE_ON only when it is required.
• SQL Comparison Toolset 4.1 includes a fix related to dependencies on SQL Server 2005. This issue occurred on some SQL Server 2008 databases when the compatibility level was set to SQL Server 2005.

...

SQL Comparison Toolset 4.0 supports the use of SQL Server 2014 with the following notes:

SQL Schema Compare

• Memory-Optimized tables. SQL Server 2014 supports a new memory table and other objects associated with it, such as:
  • a new Hash index
  • a new Range index
  • a new database filegroup that contains the memory tables

  The Comparison Options window includes a new option to support memory-optimized tables. The Compare memory-optimized tables check box is located on the Comparison Options tab under the Table Options section.

• BUCKET_COUNT property. The new BUCKET_COUNT property for hash indexes is supported.
• ColumnStore indexes . SQL Server 2014 supports a new type of index called a "columnstore," which is fully supported by SQL Schema Compare.
• XML indexes . SQL Server 2014 introduces two new xml indexes and associated enhancements, such as:
  • a new primary selective xml index
  • a new secondary selective xml index
  • new xml index namespaces
  • new xml index paths
• INCREMENTAL = ON | OFF statistic . The new statistic property, INCREMENTAL = ON | OFF is supported.
• ALTER ANY DATABASE EVENT SESSION permission . The new permission type, ALTER ANY DATABASE EVENT SESSION is supported.
• Non-supported permission types . SQL Server 2014 introduces three new permission types that have server-scope, which are ignored by SQL Schema Compare is it can synchronize only those permissions that have database-scope. These new permissions include:
  • CONNECT ANY DATABASE
  • IMPERSONATE ANY LOGIN
  • SELECT ALL USER SECURABLES
• Natively-compiled stored procedures . SQL Schema Compare 4.0 fully supports natively-compiled stored procedures in SQL Server 2014.

SQL Data Compare

• Memory-Optimized tables . SQL Server 2014 supports memory tables except for custom keys. This issue is a limitation in SQL Server 2014 itself, which does not allow updates to the primary key columns of a memory table.
• Hash indexes . Hash indexes are fully supported in SQL Data Compare, which also considers these indexes when choosing the unique comparison key.
• ColumnStore indexes . ColumnStore indexes are supported by SQL Data Compare with the following exception. SQL Server 2014 does not allow data changes on a table that contains a non-clustered columnstore index. To synchronize this index, it is disabled before data synchronization, and then enabled after the sync is complete. Note that a clustered columnstore is updatable and does not need disabling before synchronization.

...

This release includes two new options for the command line interface. The CompareMemoryTables option indicates whether you want to compare and synchronize memory-optimized tables. The CompareColumnStoreTables option indicates whether you want to compare and synchronize columnstore tables.

4.0 Fixed Issues

SQL Schema Compare

• This release fixes an issue related to missing dependencies associated with database synonyms.
• An issue causing a "System.NullReferenceException" error appearing during a comparison is resolved. this issue resulted from missing data compression in the table that contains the indexes.

SQL Data Compare

• This release fixes an issue related to extended properties on foreign keys.

3.1 New features

Schema Compare and Data Compare

The new Full Screen function allows you to maximize the user interface work area by hiding the ribbon.

Schema Compare

• Schema Compare now supports the database COMPATIBILITY level. When the SQL Server compatibility is set to a previous version of the database, Schema Compare automatically detects the version and generates the appropriate script.
• You now can compare SQL Server system databases, such as master, model, msdb or tempdb. Previously system database were excluded from the comparison. System objects are still excluded on both the user and system databases.
• Users now can save the workspace to a custom file or location.

Data Compare

• Users now can save the workspace to a new file or location.
• Users now can change the location where the temp data related to table serialization is kept during data comparison. Previously the default location was the temp folder of the current user.

3.1 Fixed issues

Schema Compare

• This release fixes an issue in the rebuild script related to tables that contain an identity column with no matching column in the target database. The rebuild script in some cases was incomplete.
• Users no longer see excluded replicated tables in a comparison. An issue caused by incorrect readings from the SQL Server system catalog, Schema Compare did not always properly identify these replicated tables and included them by mistake.
• A conversion problem that flagged some tables as "non-comparable" when comparing the char/varchar/nchar/nchar/text data types between SQL 2005 and SQL 2008 no longer occurs.
• This release fixes an issue causing the Schema Compare grid to ignore the selection in the Include check box used to include or exclude an object from the synchronization.
• The schema comparison grid no longer displays an error message when the user selects or clears numerous stored procedures check boxes.
• This release fixes an issue with the column ordinal by ensuring that the actual column position is used to determine the ordinal. The ordinal is the column position in the table. Previously, the column ID was used to determine the ordinal. Unfortunately SQL Server does not maintain or guarantee sequential values in the column ID field and sometimes contains “gap” that could trigger unnecessary schema differences.
• An issue causing some comments to not parse properly in the definition of views, procedures, or functions no longer occurs.
• An issue affecting columns with the following criteria is fixed:
  • the column does not accept a null value;
  • the column contains a default constraint; and
  • the column is synchronized via a table rebuild script.

...

• Users no longer experience an issue related to the synchronization of identity columns. The synchronization script generated in some cases explicit null or default values which are not accepted for identity columns.
• A small scripting error related to CLR DDL triggers created with “EXECUTE AS” clause no longer occurs.
• This release fixes a schema-read issue with the columns included in an index.
• A problem related to database names that contain Cyrillic letters no longer occurs.
• Users no longer experience a data conversion issue between varchar(max) and image data types.
• This release fixes a problem related to foreign keys with duplicate names. Some internal collection used by schema compare API didn’t handle the duplicates properly.
• Some minor conversion issues between the following data types no longer occur:
  • from char/varchar to float/real
  • from datetime to timestamp
• Users no longer experience an issue with full-text indexes. A missing dependency between the full-text index and the unique key/index associated with it, caused the full-text index synchronization script to fail.
• This release fixes an issue related to the serialization of bindings between the user-defined data types and rules/defaults.
• A SQL or CLR triggers issue that caused the user interface to not properly show schema differences between two triggers no longer occurs. This issue occurred in cases when the only different property was the trigger status, either enabled or disabled.

Data Compare

An issue with the data compare grid causing the View Row Details function to generate an error when no row was selected on the grid.

2.1.2 New features

SQL Server 2012 support

SQL Comparison Toolset 2.1.2 supports the use of SQL Server 2012.

...

This release includes fixes to object compare snapshots.

2.1 New features

SQL Server 2012 Testing Compatibility

SQL Comparison Toolset 2.1 is SQL Server 2012 RC0 compatible in non-production environments.

Updated License Key Activation Service

SQL Comparison Toolset 2.1 now includes an updated license key activation service.

2.0 New features

Completely Redesigned Console

New user interface design and navigation to maximize user productivity.

Expanded Comparison Options

Perform granular comparisons with new comparison options such as comparing and synchronizing views along with tables, comparing databases with different collation, variable transaction size, and many more.

New Comparison Sessions

Easily repeat frequent compare operations with one simple click using comparison sessions which contain all the data related to a comparison operation including databases, credentials, comparison options, mapping rules, and excluded objects.

Customizable Mapping Rules

Easily customize the way database objects are mapped together using new schema, name, and data mapping rules.

...