SQL Source Control 4

Migration scripts V2 beta

We're going to remove the migrations V2 beta from SQL Source Control in version 5. We're replacing it with an improved version of the original migration scripts feature, which supports more version control systems and actions.

Download the SQL Source Control 5 beta

Scripts created using the V2 beta of migrations won't be compatible with SQL Source Control 5. To learn more, see Upgrading from old versions of migration scripts.

SQL Source Control 3.6 and later includes a beta version of the new Migrations V2 functionality. This works quite differently to the V1 migration script functionality introduced in SQL Source Control 3.0.

Migrations V2 is still in beta, and SQL Source Control uses Migrations V1 by default. To use Migrations V2, you need to enable it in the engine and comparison options.

About Migrations V2

Migrations V2 supports:

  • all source control systems (including Git and Mercurial)
  • branching and merging
  • better integration with CI systems for automated deployment
  • SQL Azure databases

Unlike V1 migration scripts, V2 migration scripts don't need to be saved in a separate folder in the repository. Instead, when you commit a migration script, it's added to a table-valued function in the database. For more information, see How V2 migration scripts are used in deployment.

What do you think?

We want to hear what you think about Migrations V2.

Didn't find what you were looking for?