Allow linking to system databases
I don't think this suggestion is here already, apologies if it is! I would like to be able to link system databases (esp master) to source control as my company has a number of shared procs here. The ability to optionally exclude the normal system procs when extracting would be really useful.
-
Anonymous commented
I would really like to see this feature. We also keep a few company critical stored procedures inside the master DB.
-
Anonymous commented
We would like to use this for our SQL jobs.
-
Anonymous commented
We would like to use this for our SQL jobs.
-
Anonymous commented
We have a lot of custom stored procedures and function defined in the master and distribution databases and model db along with startup procs.
It would be very helpful to track those changes as well
-
Bret Lowery commented
Stephanie, it's not possible in the case of startup procs (procs in master flagged as startup by sp_procoption). These may be executed while user databases are still in recovery after a cold restart or cluster failover. Other than that one case though I think you are correct.
-
johndempsey commented
Hi Stephanie,
Thanks for the response.
Unfortunately, although possible, this would be a large undertaking with no perceivable business benefit and a certain amount of risk. (Some of the procs here are shared between multiple critical systems) As such, experience tells me that I wouldn't be able to get the initiative off the ground!
This is why I mentioned excluding system objects in my request.
Regards, John
-
Hi John,
Would it be possible to create a new user db and put stored procedures that are shared across teams there instead of the master? That way you could source control only the objects you cared about instead of all objects in the master db.