SQL Source Control 4

SQL Source Control 3.0 release notes



  • Performance Improvements – Static data comparisons: Now turned on by default. This will give a significant reduction in the time taken to generate a commit or retrieve list when large amounts data are source-controlled.
  • Performance Improvements – Asynchronous commits: The commit process no longer blocks the user from using SSMS when a commit is underway. Users can now perform other (non SQL Source Control) tasks in SSMS while their previous commit is completing.
  • Uninstall survey: To help us understand why users would stop using SQL Source Control, we have added an optional, simple survey at the end of the product’s uninstall process.
  • Bug fixes

Bug Fixes


{SA} SqlException (Number: 3906) @ BlockExecutor.ExecuteBlock(…)


{SA} NullReferenceException @ ConnectShared.OpenNewTab(…)


{SA} InvalidStateException @ SvnRemoteOperations/<>c__DisplayClass39/<>c__DisplayClass3b.<GetDiffs>b__38(...)


Invoking the Commit tab from the 'Tables' folder does not see all tables selected in the grid


This is a bug fix release, which includes the same ‘new’ features as v3.0.13.4178 but also fixes the following bugs:

  • SQL Compare interoperability bug
  • Problem with Check For Updates client where CFU was report the incorrect product version.

Version 3.0 - February 1st, 2012

New features

Migration Scripts
SQL Source Control 3.0 enables you to create migration scripts between two versions of a database. Migration scripts are customizable change scripts that are committed to source control and re-used in deployment by SQL Compare.This can be useful, for example, if you add a NOT NULL constraint to a column in development and want to deploy this change to another environment. If you try to deploy this change using SQL Compare, the synchronization script will fail if the target table contains data because a default value is required; you can specify this value using a migration script.

Performance improvements
SQL Source Control 3.0 includes some underlying performance improvements, and further work on this is planned for the next release. Our internal testing shows a 30% improvement in the speed of some operations.

Known issues

Migration scripts are not supported for all source control systems
Currently, you can only create migration scripts if you are using Subversion (SVN), Team Foundation Server (TFS), or Vault. If your source control system is not supported, you can request support on the SQL Source Control feedback forum.

Migration scripts backward compatibility
If you have used any of the SQL Source Control early access releases, any migration scripts you created are not compatible with version 3.0.

Getting the latest migration scripts
Migration scripts are not shown on the Get Latest tab. When you get the latest version, any applicable migration scripts are run automatically.

Dependency checking in migration scripts
When you create a migration script, SQL Source Control does not check the script for dependencies. We recommend you make sure all dependencies are included in the migration scripts you create.

Didn't find what you were looking for?