SQL Source Control versions 3.6 and later include 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. At the moment, the Migrations V2 user interface is still basic.
Because it's in beta, Migrations V2 is disabled by default. To enable it, see Enabling the Migrations V2 beta.
What's new in Migrations V2
Migrations V2 supports:
- all source control systems (including Git and Mercurial)
- frequent 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 information about how this works behind the scenes, see How V2 migration scripts are used in deployment.
What do you think?
We want to hear what you think about Migrations V2.
- Suggest and vote for ideas on the SQL Source Control user suggestions forum
- Discuss the new migrations feature in the migrations V2 Google group
- Report bugs to support
- If you find mistakes in this documentation, or it doesn't answer your questions, use the "Mistake on this page?" email link at the bottom of each page