Migrations support for Git/Mercurial
It seems that right now migrations only support SVN, TFS and Vault - none of which I'm willing to use anymore. Please consider prioritizing support for Git/Mercurial.
We use git and would prefer to not have to switch in order to use this tool.
Allow HG Source control (Mecurial/Kiln) to create migration scripts. Changes generated do not always generate the correct SQL, so it would be good to be able to modify the SQL "generated" prior to committing (which I assume is done via Migration Scripts).
Please add Git support for migration scripts
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.×.
The SQL Source Control v220.127.116.11 and I saw migration script worked in SVN but there is nothing happening when I am on GIT. is there any updates?
Josh Rogers commented
What is the status of this beta? We just purchased the Developer Bundle and we're eager to be able to use these migrations.
RedGate, any update on this since Oct? We would like to move from SVN to GIT but we need full support.
Is there an eta on this? It would make a huge difference to our team.
Peter van Rees commented
Can anyone from Redgate comment on the progress on this issue? We are using Hg and are forced to keep seperate SVN repos for the database projects only because of this issue not being solved....
You would make me very happy if this would work!
Damian Powell commented
"The [DVCS] issue is more challenging than we had anticipated, but we're completely committed to solving it as the highest priority for SQL Source Control."
Is it still highest priority? It's been a while. How about an update?
If supporting DVCSs with their non-linear histories is really difficult, why not release a half-way solution that will work with a DVCS provided it has a linear history? At the moment, we have SQL Source Control but really aren't getting the most out of it, even though our DB history is completely linear.
Julian Price commented
Very disappointed to find that data migrations are not supported for Git. Hope it will be added soon.
Hi Stephanie, This is a feature our company is waiting on because we have to move over to GIT but Red Get is not supporting the migration feature. So, the entire process is on hold and we are thinking of alternatives.
Adam Swann commented
You've likely got 9 new users on this end once you make this happen.
Mike Hanrahan commented
q42jaap, if (and I may be wrong) you are responding to my statement, I didn't mean to suggest that it was a no brainer technically....I have no doubt that it is very difficult, but it should a no brainer in terms of priority for the product. It is a great product, but hard to justify purchasing it for our whole team until it supports this feature.
Jeff Jones commented
Good news, looking forward to using it.
It's not that simple as it seems, things like git flow, branches etc make things more difficult. The shared database vs dedicated database further complicates things. Let's be patient!
Joe Kearney commented
Are there any updates to this? Any expected date of release? David, from your last comment it looks this might yet take some time – is that a fair prediction? Thanks
Mike Hanrahan commented
Redgate - Any updates on timeline for this??? Seems like a no brainer!
Roman Pyzh commented
Any updates on the timeline?
This is a requirement for purchase
I'm also adding a vote for Git Migrations support. Can't buy this without it.
AdminDavid Atkinson (Admin, Red Gate) commented
It's still very much on the forefront of our minds and we're still very committed to solving the problem of automating the generation of database changes. The differences between DVCS and "traditional" source control systems, particularly the non-sequential revision numbers, have a bigger architectural impact that we had first anticipated, which has meant a re-think on how we might implement our solution.
Jamie Clayton commented
Almost March 2013, 8 months after the August 2012 release date. Must be very close by now or has Red-gate forsaken this commitment?
Reuben Greaves commented
Any ideas on the anticipated release for this feature yet?