SQL Data Compare download

v14.5 [Apr 16, 2021]
Internal library updates.

v13.8 [Jan 20, 2020]
- Faster script parser - scripts folders should load data much faster from all tables.
- New command line error code - 60 - for the state where there are no comparable tables/views. This would previously have returned error code 63, which now only covers identical databases.

v12.3 [May 8, 2017]
Features:
- The "My Projects" window can now be opened from the toolbar.
Fixes:
- When using the SQL Source Control data source and comparing custom-linked databases, the revision fields are now correctly disabled.
- SC-9399: When using the SQL Source Control data source, progress updates will now be displayed while the requested revision of the scripts folder is being checked out.
- Changes to a comparison report's name will now be correctly used if the report is generated while the "name" field still has focus.
- SC-9433: Fixed a bug which could prevent the sqlcompare.exe commandline from recognising /options:IgnoreIndexes in some deployment cases.

v11.6 [May 16, 2016]
May include unspecified updates, enhancements, or bug fixes.

v11.4 [Dec 10, 2015]
May include unspecified updates, enhancements, or bug fixes.

v11.3 [Sep 21, 2015]
May include unspecified updates, enhancements, or bug fixes.

v11.0 [Oct 11, 2014]
October 6th, 2014
Features
Support for SQL Server 2014 object types
You can use SQL Compare 11 to compare and deploy:
memory-optimized tables
natively compiled stored procedures
memory-optimized table types
Icon
When you deploy a database containing memory-optimized objects (memory-optimized tables, natively compiled stored procedures and memory-optimized table types), we recommend you perform two deployments. See Deploying memory-optimized objects.
clustered columnstore indexes
incremental statistics
Icon
If the ‘Ignore filegroups, partition schemes and partition functions’ project option is selected, the deployment of incremental statistics might fail if they rely on partition schemes or functions which are being ignored.
Backup commands in the deployment script
When you select the 'Back up before deployment' option in the deployment wizard, the backup commands are now included in the deployment script:
This means you can now back up the target when you create a deployment script to run in Management Studio.
Icon
SQL Compare 11 no longer supports SQL Backup Standard or SQL Backup Lite.
‘Do not add error handling statements to deployment scripts’ project option
When you run the deployment script in Management Studio, this option allows the deployment script to fail when an error is encountered. You can only select this option if transactions aren't used in deployment scripts.
When you deploy directly from SQL Compare, the deployment is always terminated when an error is encountered.

v9.1 [Dec 20, 2011]
SQL Server 2000, 2005, 2008 & SQL Azure databases
Native & compressed SQL Server 2008 backup files
SQL Server 2000 & 2005 backup files
Red Gate SQL Backup files
Folders of SQL scripts (for source control)

v9.0 [Nov 7, 2010]
Generate T-SQL scripts to update one database with the contents of another
Quickly fix problems by restoring damaged or missing data to a single row
Keep an accurate history of all previous database records
Compare and synchronize data within SSMS
Deploy to SQL Azure databases