SQL Source Control is intended to connect your database to a repository such as Git for you to then commit and store objects and keep track of changes that have been made, you can also track history as shown in the document here:
If I'm understanding publishing databases after approval, to mean deployment, then SQL Source Control doesn't provide that in a simple manner. I would advise taking a look at SQL Compare which is designed for deploying database changes to specific targets.
wangxs
Posts: 1 New member
Answers
SQL Source Control is intended to connect your database to a repository such as Git for you to then commit and store objects and keep track of changes that have been made, you can also track history as shown in the document here:
https://documentation.red-gate.com/soc/common-tasks/view-source-control-history
If I'm understanding publishing databases after approval, to mean deployment, then SQL Source Control doesn't provide that in a simple manner. I would advise taking a look at SQL Compare which is designed for deploying database changes to specific targets.
https://documentation.red-gate.com/sc
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?