These pages cover SQL Source Control 3. Help for older versions is also available.

SQL Source Control includes an optional beta version of the improved migration script feature. We'd love to hear what you think.

Skip to end of metadata
Go to start of metadata

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

SQL Source Control still uses Migrations V1 by default. To enable Migrations V2, see Enabling the Migrations V2 beta.

What's new in 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, they are added to a table-valued function in the database when you commit them. 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.

  • No labels