Create migration script without changes to any database objects
It would be great if you could add just a migrations script to your source control without any related change to any object in the database. This would be very use ful when tyou have tabel A with column 1 and 2 and i column 2 you want to replace all 'A' with 'a' or something.
Provide a way to check in a SQL Script that changes Data as an migration script without any schema or static Data changes.
That will help us track all our changes to the database and maintain proper order.
Migrations without requiring changes to objectsl (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.×.
Hi Guys, very good product but does not make any sense if it is not creating any migration script for for Data Change. Please fix it asap or lose customer.
I am also trying to implement the automated deployment. But I am not able to integrate the custom script to source control. I think this is very important for automation. Any one from please let us know what is the ETA for this? .
Ther's another suggestion for the same thing with more votes already. https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2565864-create-migration-script-without-changes-to-any-dat
Brendan Stewart commented
Simon de Kraa commented
We need this functionality as well. We use Workflow Foundation and store the Workflow definitions in the database. Having the correct definitions is essential.
At the moment you get the following error message: http://imageshack.us/a/img32/8915/datamigration.jpg.
Brad Wood commented
Yes, please. Every release we have back fill scripts that affect non-static data and this is causing an issue for us now that we are trying to completely automate our DB deployments and need EVERYTHING committed as a migration script.
See this thread I started on the topic (before I found this User Voice request):
AdminDavid Atkinson (Admin, Red Gate) commented
The workaround for this is to prefix or suffix the code to a schema change. It's not ideal, but should work. Please vote for this issue if it affects you and hopefully we'll be able to implement a better fix.