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…)
    Nick shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  AdminElizabeth Ayer (Admin, Redgate) responded  · 

    I am delighted to let you know that this is now released! Migrations support for Git/Mercurial is available – out of beta – in SQL Source Control 5.

    If you’re new to SQL Source Control, you can try it out free for 28 days by downloading it from

    If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.

    You can see Migrations examples and tutorials here:

    Thank you for your continued support, and please let us know if you have further feedback on this capability, or any others, in SQL Source Control!


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

        We are aiming to release SQL Source Control 5 at the end of May.

        The beta program has closed but you can try the release candidate:

        However, please be aware that following the release of SQL Source Control 5, the RC would stop working, and you would need to upgrade to continue using the new migrations feature (if you downgrade, any migration scripts created with the RC would be ignored)

      • AdminAdam (Admin, Redgate) commented  ·   ·  Flag as inappropriate

        Hi Dave,

        Thanks for alerting us to that. We have reproduced this when downloading using Internet Explorer - when it gets downloaded the file extension is no longer .exe.

        As a workaround you can rename it after downloading so that the file name ends in .exe

        I hope that fixes it for you immediately while we work on fixing the issue.


      • Dave Bennett commented  ·   ·  Flag as inappropriate

        I just went to download the beta and the file I end up with is uninstallable. I figured it was a compressed file, so I decompressed it, and I can find no installer in the file anywhere. Tried it 4 times with identical results.

      • AdminElizabeth 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.

      • Micky 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. :)

      • Peter 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 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 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.

      • John 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 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.

      • Anonymous 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.

      • Rob commented  ·   ·  Flag as inappropriate

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

      • Peter 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 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 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 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.

      ← Previous 1 3 4 5

      Feedback and Knowledge Base