Release notes - version 3.0

SQL Source Control is an add-in for SQL Server Management Studio that allows you to source control your databases.

Note that SQL Source Control is not a source control system; it allows you to store your databases in your existing source control system.

This article discusses:

Version 3.0 of SQL Source Control introduces the following 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.

SQL Source Control version 3.0 has the following 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 Controlfeedback 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.

You are recommended to ensure that all dependencies are included in the migration scrtipts you create.