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…)

Need to deploy from Git Source Control Repository to Target Databases

Need to deploy from Git Source Control Repository to Target Databases

I use a shared Dev database and I work on multiple issues and versions of our software at the same time and am using Git to keep track of all the changes that go with each issue I'm working on. However, when QA asks me to deploy the changes relating to one specific issue to their QA environments, I have to manually go through all the changes in our shared database and determine which of the changes I made relate to that issue. In Git, I create a branch for each issue and check in my changes for each issue to its corresponding branch. However, RedGate Source Control cannot at this time deploy to a Target database by using these Git branches as a source. This would be a major time saver!!!

14 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…)
Sam Bendayan shared this idea  ·   ·  Report…  ·  Admin →
declined  ·  AdminMichael Upton (Development Lead, Redgate) responded  · 

These kinds of deployment scenarios are handled by SQL Compare (for manual deployments) or SQL Change Automation (for more automated/scripted deployments). SQL Source Control is intended for the dev side of your database change management process, linking your development database to a version control system.

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
  • AdminDavid Atkinson (Product Manager, Redgate) commented  ·   ·  Report

    One ways of doing this if you have a build tool is to set up a Build to use SQL CI Sync to deploy changes from source control to your QA environment. Even better is to use a release management tool such as Octopus Deploy so your deployments to QA can double as rehearsals for actual deployment. Failing this, you should be able to use SQL Compare with Source Control/Scripts Folder as the source datasource, pointing it at your Git working folder.