How can we improve SQL Source Control?

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.

935 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    NickNick shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    GregGreg shared a merged idea: git Migration scripts  ·   · 
    JackieJackie shared a merged idea: Add git support for migration scripts  ·   · 
    Jamie ClaytonJamie Clayton shared a merged idea: Allow HG Source control to create Migration Scripts  ·   · 
    Chris HerringChris Herring shared a merged idea: Migrations support for git  ·   · 
    started  ·  Elizabeth AyerAdminElizabeth Ayer (Admin, Redgate) responded  · 

    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.


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      • Elizabeth AyerAdminElizabeth Ayer (Admin, Redgate) commented  ·   ·  Flag as inappropriate

        Mercurial support today is through a working folder, and the new migrations will work with the working folder option. However, because we can't commit to fixing VCS-specific issues with Mercurial (which we would with Git), we really didn't want to keep you guys hanging on even longer.

        If you're interested, our best estimate is that less than 2% of SQL Source Control users today link their database to a Mercurial repository.

      • MickyMicky commented  ·   ·  Flag as inappropriate

        I would agree that Git is more popular, but do you know what your current customer base uses? We use Mercurial. I wonder how many of your other customers use Mercurial and would appreciate support. Just my two friendly cents. :)

      • PeterPeter commented  ·   ·  Flag as inappropriate

        Wow, no mercurial, that is a real shame. I am out then... Would like to have known that a bit earlier.

      • Doug TuckerDoug Tucker commented  ·   ·  Flag as inappropriate

        Any chance of splitting this into separate feature requests, one for Git and one for Mercurial? My development team has since given up on Mercurial and switched to Git. Unless the underlying process is identical, it would seem important to be able to prioritize fully supporting either Git or Mercurial, depending on customer interest.

        A status update would be greatly appreciated!

      • Git AdvocateGit Advocate commented  ·   ·  Flag as inappropriate

        This probably isn't going to happen. It has been almost four {4} years since the original request and no changes.

      • JohnJohn commented  ·   ·  Flag as inappropriate

        The SQL Source Control v3.6.0.3 and I saw migration script worked in SVN but there is nothing happening when I am on GIT. is there any updates?

      • Josh RogersJosh Rogers commented  ·   ·  Flag as inappropriate

        What is the status of this beta? We just purchased the Developer Bundle and we're eager to be able to use these migrations.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        RedGate, any update on this since Oct? We would like to move from SVN to GIT but we need full support.

      • RobRob commented  ·   ·  Flag as inappropriate

        Is there an eta on this? It would make a huge difference to our team.

      • Peter van ReesPeter van Rees commented  ·   ·  Flag as inappropriate

        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 PowellDamian Powell commented  ·   ·  Flag as inappropriate

        "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 PriceJulian Price commented  ·   ·  Flag as inappropriate

        Very disappointed to find that data migrations are not supported for Git. Hope it will be added soon.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Mike HanrahanMike Hanrahan commented  ·   ·  Flag as inappropriate

        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.

      • q42jaapq42jaap commented  ·   ·  Flag as inappropriate

        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 KearneyJoe Kearney commented  ·   ·  Flag as inappropriate

        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

      ← Previous 1 3 4 5

      Feedback and Knowledge Base