The SQL Source Control 5 beta includes an improved version of the migrations feature, based on the version that first launched with SQL Source Control 3 (aka ‘Migrations v1’).

Migration scripts now work with Git, as well as all other version control systems, and we’ve made a bunch of extra improvements, including:

• Support for merging multiple branches
• Data-only migration scripts
• The option to deploy even if you’re not connected to your code repository

Because we are in final preparations for release, the beta program is now closed to new participants.

You can still look forward to the full release in SQL Source Control 5 in Q2, 2016.

I have some good news for you! We’ve just released the SQL Source Control 5 beta, which includes an improved version of the migrations feature, based on the version that first launched with SQL Source Control 3 (aka ‘Migrations v1’).

Migration scripts now work with Git, as well as all other version control systems, and we’ve made a bunch of extra improvements, including:

• Support for merging multiple branches
• Data-only migration scripts
• The option to deploy even if you’re not connected to your code repository

You can sign up and download it here: http://www.red-gate.com/products/sql-development/sql-source-control/entrypage/sql-source-control-beta

We want your feedback to improve the feature ahead of the full release in SQL Source Control 5 (still expected Q2, 2016).

We want to apologize for how long it’s taken to update this status. We’re really sorry, and we recognize how frustrating it must have been.

We did start work on this feature request, with the Migrations v2 beta. But that solution was hard to use: you had to write complex scripts that would work on any version of the database. The scripts were hard to write and understand, so even experienced SQL developers found that errors crept in.

We realized that approach wasn’t good enough, and we’ve started work on a better solution. It’s based on migrations v1, but will:
• work with Git
• allow merging
• correctly flag up conflicts in migration scripts
• allow data-only migration scripts (scripts that aren’t linked to specific schema changes)
• not require a separate repository
• allow deployment even when not connected to the code repository

Because Git has become far more popular than Mercurial, we’re no longer planning to support migrations with Mercurial.

We apologize again, both for the false start and not keeping you informed. From now until release, we’ll keep you updated on the progress of this request.

Please hang in there: active development is underway and we’ve started alpha testing. We’re planning to release a production version of migrations in SQL Source Control 5, expected Q2, 2016. In the meantime, please keep talking to us to help us make the right decisions about this feature.

Migrations for Mercurial (migrations v2) can now be used throughout the delivery lifecycle with the latest versions of the Red Gate SQL tools. SQL Source Control, SQL Compare, SQL CI and Deployment Manager all use migrations v2 scripts if configured to do so.

NB. We’re still calling the migrations feature a beta feature within the products. This is because we are continuing to release user interface improvements and improve stability, and we do not yet consider the feature complete. However the core products have been through their full testing and release processes and are stable.

A frequent releases channel for SQL Source Control is now available, and it is this channel that contains the migrations v2 feature. This means you can evaluate the new migrations functionality without having to install a beta version of SQL Source Control, and you will benefit from the regular updates being made to SQL Source Control.

SQL Compare 10.6 (currently in beta) supports migrations v2 scripts. The migrations v2 feature must be enabled on the options tab. Migrations v2 are enabled by default in SQL CI (part of the SQL Automation Pack) and in Deployment Manager.

We’d really like to hear about your experiences so we can fix issues and try to make any updates you need before the final release.

Download links for SQL Source Control and SQL Compare with migrations v2 and, along with instructions on how to enable migrations v2 are on http://www.red-gate.com/migrations

Please note that if you have previously installed the standalone migrations v2 beta versions of SQL Source Control (version 3.9.x) or SQL Compare (10.9.x) you will need to uninstall these in order to install versions 3.6.×. and 10.6.×.

An Beta release of SQL Source Control is now available, which supports Migrations for Mercurial.

You can download at http://www.redgate.com/migrations

We have also released a beta for SQL Compare. which is aware of Migrations v2 scripts and will apply these to target databases.

NOTE: This is a Beta release and is not fully tested or functionally complete yet. It would be great if you could try it in a test environment and let us know about your experiences so we can fix any issues and try to make any updates you need before the full release.

An Early Access Release of SQL Source Control is now available, which supports Migrations for Mercurial. To download, please see http://documentation.red-gate.com/display/MV2.

NOTE: This is an Early Access Release and is not fully tested or functionally complete yet. It would be great if you could try it in a test environment and let us know about your experiences so we can fix any issues and try to make any updates you need before the full release.

Thank you!
Stephanie Herr :-)
SQL Source Control Product Manager

A subset of the team has been working on this issue and we think we have a solution (on paper). We are starting a technical review with the entire development team to see if it is feasible.

I do not have an expected release yet, but will update this suggestion as we progress.

We have started to add Migrations support for Mercurial and hope to complete this work by mid-August 2012.

The current plan is to add Migrations support for Git following the completion of this work.