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 introduced in SQL Source Control 3.0, and works quite differently behind the scenes.

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, 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.