Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control: Support Additional Source Control Systems

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Stop treating Git like a red-headed step child.

GIT seems to always get the short end of the stick. Can't do Object Locking, can't do Migrations, can't do Get Latest, can't View History.

Please stop treating GIT like the middle child in the Brady Bunch. GIT is totally Marsha, not Jan.

13 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Paul E. Kahl shared this idea  ·   ·  Report…  ·  Admin →
completed  ·  AdminMichael Upton (Development Lead, Redgate) responded  · 

I love your request to much, I’m going to hate to close it as finished soon….

Git is a first-class citizen in SQL Source Control 4.1, which is scheduled to go out within a couple of weeks. You can get it right now if you sign up to the ‘Frequent Updates Channel’ (instructions here: https://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates).

We’ve added Commit, History, Push and Pull (Pull+Apply changes = Get Latest) for Git.

Object locking can be used with Git, but it’s a database-level thing, so is really only useful if you have multiple people sharing a database – a relatively uncommon set-up for Git users.

The latest version of Migrations, in SQL Source Control 5, now supports all version control systems, including Git.

Since that covers every item on your list, I’ll mark this as completed – but thanks for making us giggle too.

Mike Upton
Technical Lead | SQL Source Control

Show previous admin responses (1)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Neil Palmer commented  ·   ·  Report

    Is there push support beyond the button in the warning message after a commit?

    It feels a little clunky to have to switch back to the previous window and click a warning message in order to use it!

  • Paul E. Kahl commented  ·   ·  Report

    So I've just finished re-linking my databases, and I've noticed something rather... Disconcerting. They're all "Dedicated" now, when they were shared before. Yes, I gained all the nifty new functionality, but "Dedicated" isn't true. The database doesn't exist on my machine, and should be a shared instance, as multiple devs on my team all use it and change it at the same time.

    However, if I select GIT while doing the re-linking, there is no option for 'shared'. The only way to get it is the old method of selecting "Other", and then "Custom", and having SSC use my local repository folder.

    So, basically, this problem isn't really resolved.

  • Paul E. Kahl commented  ·   ·  Report

    I was at SQL In The City yesterday, when this was explained to me, and I think it's awesome! The only sad part for me was that I needed to re-link all my databases to get the new features. That said, relinking was less painful than my first tattoo.