version 4.0.5.0
Release date: May 07, 2012.
- Fixes a problem that occurs when the first column of a data candidate key is created as a descending column.
- Fixes a problem with the data candidate index defined on columns that allow NULL values.
version 4.0.4.0
Release date: April 17, 2012.
- Fixes an issue with Data Compare Command Line foreign key option.
- Fixes a problem with the licensing component that occurred on a Windows configuration that enforces FIPS-compliant cryptography algorithms.
- Fixes an issue with large varbinary(max) data type columns defined with FILESTREAM property.
version 4.0.1.5
Release date: October 10, 2011.
Minor improvements and fixes
- Allows UI session naming without launching it
- Adds a tooltip to the session panel that shows the left/right databases
- Fixes an issue with the main screen resizing
- Fixes an issue with text wrapping during print/preview
- Adds a UI formatter for XML data type
- Improves the comparison based on specific tables/views
version 4.0
Release date: July 06, 2011.
SQL Data Compare redesigned from the ground up
- Graphical user interface has been completely reworked to reflect the latest standards in user interface design
- Improved, simplified workspace that provides for a one click re-compare eliminating the hassle of repeatedly configuring comparison sessions
- Improved memory management eliminates any database size limitations due to memory constraints. Custom built algorithms handle serialization of both data rows and script fragments as needed
- Non-critical errors are registered and reported but do not stop the data comparison operations
- Many new options have been added like the ability to compare views, ability to compare databases with different collations, variable transaction size etc
- Mapping Rules allow the user to customize the way the database objects are paired together. Mapping rules include schema mapping, object name mapping and data type mapping
- In addition of the data type compatibility the new SQL Server Data Compare provides for validating the uniqueness of the selected comparison key
- The script for large fields is generated in fragments of a predefined size and sent to SQL Server one block at a time
version 3.5
Release date: May 26, 2010.
SQL Server 2008 R2 support and functional enhancements
- Support for SQL Server 2008 R2
- The passwords for SQL Server connections are now encrypted and stored in the workspace file eliminating the need to enter passwords every time you launch xSQL Object
- An issue with early expiration of xSQL Data Compare trial period on Windows Vista and Windows 7 when the UAC is turned on has been addressed
- Enhancements and fixes in the SQL Data Compare Command line utility including a new error code that tracks script execution errors
- Explicit updates of the identity columns are no longer supported and will trigger data warnings
version 3.0
Release date: October 06, 2008.
SQL Server 2008 support
- Support for SQL Server 2008 added
- All new SQL Server 2008 data types like date, time, datetime2, datetimeoffset, geography, geometryand hierarchyID are supported
- Spatial data types, geography and geometry are synchronized using Well-Known Text (WKT) representation
- Improved support for CLR data types on Sql Server 2005 and Sql Server 2008 databases
version 2.5
Release date: April 16, 2007.
SQL Server 2005 support
- Support for SQL Server 2005 added
- Tested with Vista and 64 bit systems
- Improved handling of very large scripts – tightly controlled resource consumption
- Command line utility for unattended comparison and synchronization
- Additional comparison options have been exposed on the interface to give users more control over the process
version 1.0
Release date: November 01, 2004.
SQL Data Compare V1 - compare and synchronize data in two SQL Server databases
- Compare whole databases or select just some of the tables
- Drop/add constraints during the synchronization process so that data being updated does not get rejected by SQL Server
- Order tables in the synchronization scripts by FK-PK relationship to avoid data integrity violations. Unlike other tools that rely only on FK drop and add, xSQL DataCompare performs the synchronization by updating data objects in the right order
- You pick which unique constraint or index will be used as the key for the comparison
- Compare/synchronize selected rows only by applying a where clause on each of the tables in the comparison