How can we improve SQL Source Control?

Include Ad Hoc Scripts in SQL Source Control

Whether server configuration, replication scripts, SQL agent Jobs, Powershell, or just test scripts, give me a folder in VCS that I can store and retrieve scripts from. Even if this is to/from a specific folder on my machine, make this an easy process to keep development code with my database.

67 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Steve Jones shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Jerome commented  ·   ·  Flag as inappropriate

    Ideally, can we have some options as to what we want set in SQL Source control. For example, Agent Jobs, Integration Services, Linked servers etc..

    One of the value of the application is the seamless script for creating the code in say, GIT.

  • Amy Eslinger commented  ·   ·  Flag as inappropriate

    I'm evaluating SQL Source Control and am now questioning whether the product will work for my company without the ability to check-in other scripts. We completely need to check in our SQL Agent Jobs and data update scripts that are now just stored on a network drive.

Feedback and Knowledge Base