Date: Fri, 29 Mar 2024 10:20:03 +0000 (GMT) Message-ID: <23619693.631.1711707603647@ip-172-31-38-4.eu-west-1.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_630_2051027298.1711707603641" ------=_Part_630_2051027298.1711707603641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
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 migr= ations feature that supports more things (including Git, branching, and mer= ging).
We'll be publishing more information about this soon.
SQL Source Control 3.6 and later includes a beta version of the new
Because Migrations V2 is still in beta, SQL Source Control uses Migratio= ns V1 by default. To use Migrations V2, you need to enable it in the engine and compari= son options.
Migrations V2 supports:
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 migrati= on script, it's added to a table-valued function in the database. For more = information, see How V2 migration scripts are used in deployment.= p>
We want to hear what you think about Migrations V2.