Releases of SQL Source Control after 1st May 2017 will no longer support SourceGear Vault as a fully-integrated version control system. 

Existing Vault users can continue to use SQL Source Control by re-linking any databases currently linked to Vault using the Working Folder method.

Why are we doing this?

Supporting Vault as a fully-integrated version control system adds complexity to SQL Source Control. We believe that removing fully-integrated support for this particular version control system simplifies the product and makes it easier to develop, test, and support.

Using the working folder method has the benefit of being able to use any version of Vault with SQL Source Control.

Keeping Vault working

Existing Vault users can continue to use SQL Source Control by re-linking any databases currently linked to Vault using the Working Folder method. 

When linking via working folder, SQL Source Control will script out the schema of a linked database to a folder on disk. This can then be version controlled using the Vault client tools, the same way as other non-database files. 

SQL Source Control's view source control history feature is not available when a database is linked using working folder. To view the history of the repository you will have to use Vault's history viewer.

What to do next

To continue using Vault with SQL Source Control, you should switch to the method suggested above. This means that Vault will to continue to work when fully-integrated support is removed in releases after 1^st May 2017.

If you need more information or help, contact support@red-gate.com.