Allow migration script to be added even if I don't want to check in all dependant objects
When I try to create a migration script on a (not yet checked in) object, and that object has a dependency on another object, then SQL Source Control requires that I add the dependent objects to the migration script and the subsequent checkin. SQL Source control is correct that there's a SQL-level dependency between the two objects, but as a developer, I can tell that it's safe to check in one without the other.
As a workaround, if I checkin the change first without the migration script, SQL Source Control suggests that I also checkin the dependent objects, but doesn't require it. I can then add a migration script to the already-checked-in change.
I'd like to avoid using this workaround and be able to directly add a migration script and not include dependent objects.
Wesley Smith
shared this idea
-
Ruchika
commented
Hi Wesley,
Thanks for your feedback! There isn't a plan to work on Migrations v1 going forward. Instead, we're working on a new approach to solve migrations that would involve running all the migration scripts upfront. The reason for working on Migrations v2 is that we want to extend migration support for Git, Mercurial and other Distributed Version Control Systems. Migrations v2 will also support Azure databases, and will integrate well with CI systems for automated deployment. The beta is available for download here: http://documentation.red-gate.com/display/MV2
You're welcome to join our development discussions if you're further interested: https://groups.google.com/forum/#!forum/red-gate-migrations
Let me know if this has raised more questions than answered :- )
Thanks,
Ruchika