SQL Data Compare 11.1 release notes
Published 26 November 2014
11.1.13 - April 29th, 2015
- Project options are now listed in alphabetical order.
11.1.11 - April 8th, 2015
SC-7837: SQL Data 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, Data Compare no longer produces excessively large log files in this situation.
11.1.10 - April 1st, 2015
SDC-1642: SQL Data Compare will trim file names generated for deployment scripts if they would exceed the maximum Windows path length.
1.1.9 - March 25th, 2015
SC-7750: Using the <Create Database...> command no longer causes an error when the other side of the comparison is a backup or source control repository.
SDC-1525: Arguments to the
/Excludecommand line switch are no longer case sensitive.
11.1.8 - March 20th, 2015
Note - SQL Data Compare 126.96.36.199 was withdrawn due to some UI issues which have been resolved in 11.1.9.
The command line version of 11.1.8 included in the DLM Automation Suite wasn't affected by these issues. This version includes the bug fixes that are also in 11.1.9.
11.1.6 - February 25th, 2015
SC-7647: Temporary files are now generated less often and cleaned up more reliably
SDC-981: Temporary files will now be cleaned up when creating a backup in the deployment wizard
11.1.3 - January 29th, 2015
SQL Data Compare now has an opt-in Frequent Updates channel.
SQL Data Compare updates are normally released every three or four months. If you want to get updates more often, you can turn on Frequent Updates. We recommend Frequent Updates if you want to:
- get new features, performance improvements and bug fixes as soon as they're available
- test new versions and help make sure they're stable
- give feedback on new features and help improve Redgate tools
Installing an update is always optional.
Read more about Turning on Frequent Updates.
SDC-1826, SDC-1833: Editing column mappings no longer causes a NullReferenceException error.
11.1.0 - November 26th, 2014
The command line has a new switch and a new option. You can use these with the SQL Packager 8 command line utility.
You can use this switch as the target data source. This is useful if you want to use the SQL Packager 8 command line utility to generate a package that will create a new database.
You can use this option if you need to create a package that upgrades a database, and if as part of the upgrade you're adding a new table containing data. When you create the data script to package, the new table won't yet exist, so you need to use this option to specify that the table will exist by the time the data script is run.