Page History

...

• 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.

The default constraint in some cases was ignored by the 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

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

2.1.2 Fixed issues

• Object comparisons of tables now complete without error when tables include either a check constraint or default constraint that depends on user-defined functions.
• The data compare command line now properly parses the ForeignKeyAction option.
• Data comparisons no longer incorrectly flag rows as different when the first column of the data candidate keys (primary key, unique constraint, or unique index) is created as a DESCENDING column.
• Data compare synchronization scripts now execute properly when:
  • Unique keys defined on columns allow NULL values.
  • Varbinary(max) columns were created with FILESTREAM attribute.
• Data compare now properly handles licensing on Windows configurations that enforce FIPS-compliant cryptography algorithms.

2.1.1 Fixed issues

This release includes fixes to object compare snapshots.

2.1 New features

SQL Server 2012 Testing Compatibility

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

Updated License Key Activation Service

IDERA 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.

2.0 Fixed issues

• Enhanced support for comparing large databases. Enhanced memory utilization, custom algorithms, and a new user interface improve the performance when comparing large databases.
• Improved Error Handling. Improvements to the error handling allow for non-critical errors to be logged, but not stop the data operations. A full error log is created and saved for review and analysis.
• Enhanced data handling. SQL Data Compare now uses SQL native types instead of .NET types to read the data from SQL Server databases which provides faster read time and mirror database types.
• Improved Scripting. SQL Data Compare has improved scripting of binary fields and large text fields.

Save

Save