By default, SQL Source Control uses the V1 migration script functionality. To use the Migrations V2 beta, you need to enable it by editing a config file and setting a comparison option.

 Warnings

Migrations V2 is still a beta feature, so we can't guarantee it will work flawlessly just yet.

• The beta automatically reports feature usage to Redgate. This is anonymous and doesn't contain any personal information. 

• The user interface is basic.

• The V2 beta doesn't recognize V1 migration scripts. (Your V1 migration scripts won't be deleted.)

• Because it's still in beta, we don't recommend you use Migrations V2 for production.

• Make sure everyone working on the same database is using the same version of the migrations feature. If different developers use different versions (ie V1 and V2), migration scripts won't run.

If you just want to experiment with Migrations V2, we recommend you create a new database in a new repository.

Enabling the Migrations V2 beta

1. Make sure you're updated to the latest version of SQL Source Control. To do this, you might need to turn on Frequent Updates.
2. Go to the SQL Source Control config files folder. By default, this is located at %localappdata%\Red Gate\SQL Source Control 3

3. Open RedGate_SQLSourceControl_Engine_EngineOptions.xml in a text editor.

4. Inside the <EngineOptions> tags, add:

   <UseMigrationsV2>True</UseMigrationsV2>

   It should look like this:

   <EngineOptions version="3" type="EngineOptions">
   	<UseMigrationsV2>True</UseMigrationsV2>
   </EngineOptions >

5. Restart Management Studio.

Enabling Migrations V2 in SQL Compare

If you want to use Migrations V2 with SQL Compare, you need to enable it in the SQL Compare project options.