43 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Adam Swann commented  ·  April 9, 2013 9:13 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  You've likely got 9 new users on this end once you make this happen.

• Jeff Jones commented  ·  April 8, 2013 5:20 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Good news, looking forward to using it.

• Joe Kearney commented  ·  April 8, 2013 1:36 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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

• AdminDavid Atkinson (Admin, Red Gate) commented  ·  February 27, 2013 2:13 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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  ·  February 26, 2013 6:15 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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  ·  February 13, 2013 7:05 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Any ideas on the anticipated release for this feature yet?

• Nathan commented  ·  January 30, 2013 9:18 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  If the difficulty with this feature request has been determining what changes are already applied to the database and what changes still need applied, then I would find it acceptable to have a version tracking table on the database.

  With that tracking table, would this feature be more straight forward?

• Greg Engle commented  ·  January 30, 2013 7:30 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  please add this support. The flexibility of being able to jump around from branch to branch in mercurial is priceless. This is a completely different mindset from SVN.

  I should be able to start a feature branch, put it on hold and switch gears to another feature branch at anytime.

• Hein Albrecht commented  ·  January 14, 2013 11:21 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  any news?

• AdminDavid Atkinson (Admin, Red Gate) commented  ·  December 7, 2012 9:34 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I can confirm that we have put the wheels in motion and we're just beginning to completely understand the extent of DVCS and branching complexity. The issue is more challenging than we had anticipated, but we're completely committed to solving it as the highest priority for SQL Source Control.

• John O'Brien commented  ·  December 6, 2012 6:00 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Any updates on this feature?

• AdminDavid Atkinson (Admin, Red Gate) commented  ·  November 14, 2012 10:05 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We only commmit. We don't do the push. However, you can edit the commandhooks xml file and make any custom changes to suit the behavior you're looking for. Please email support@red-gate.com if you need help doing this.

• Oli commented  ·  November 14, 2012 8:32 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Is it normal presently with Mercurial that when I commit changes in the Red Gate Window In SQL Server, the "phase" is at "draft" and it isn't pushed to the server? Is that a setting I forgot? If it's normal, than it would be a good thing to add it in the next release!!

• Golden Tamarin commented  ·  November 6, 2012 1:03 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Based on the rate of grow. Git/Mercurial represent the future.
  Migration support for Mercurial would be a very good choice.

• hznkgt commented  ·  October 2, 2012 8:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  git is a good version control system.
  I like it ,and hope it can be supported earlier

• AdminDavid Atkinson (Admin, Red Gate) commented  ·  September 17, 2012 7:57 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hi,
  The revised target is to get this out by the end of the year. Some unanticipated circumstances beyond the control of the project team have conspired against our earlier estimate. Our sincere apologies for the delay.
  David

• Anonymous commented  ·  September 17, 2012 7:26 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Would appreciate an update on release date for this feature.

• Mike Lehner commented  ·  September 10, 2012 11:43 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  +1 for git migrations. We could have used Mercurial for our DB projects but our other departments (Web) are already working with Git and after using it seems to fit better into our workflow.

• Jamie Clayton commented  ·  September 9, 2012 9:10 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  David, Chris, Do you have a revised delivery time-frame?

• AdminDavid Atkinson (Admin, Red Gate) commented  ·  August 21, 2012 4:37 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Due to circumstances beyond our control, the mid-August date will not be met. My sincere apologies for this bad news. I will update this thread once we have a new estimate.