Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

Stored Procedure & 'other' database Expand / Collapse
Posted Wednesday, November 21, 2007 6:51 AM


Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,661, Visits: 23,078
Dealing with this as a deployment issue would probably be the best approach. Create a process or an application that will apply changes across all of the databases. Once approach to this may be to create a single database with just your stored procedures in it and a process that replicates all of the procedures to your other databases when a ddl event fires. This could be managed pretty easily through triggers or even SQL replication and would ensure nothing ended up out of sync.

Regardless of how you do this, I would try to establish this type of infrastructure right away and make sure everyone sticks to it.
Post #424578
Posted Wednesday, November 21, 2007 6:58 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 27, 2009 8:11 AM
Points: 5, Visits: 14
Thanks for your input, it's much appreciated!
Post #424581
Posted Thursday, November 22, 2007 12:35 AM


Group: General Forum Members
Last Login: Monday, June 3, 2013 9:53 PM
Points: 433, Visits: 619
"You are not likely to run into errors from adding procedures to the master database"... umm, maybe/maybe not. Master is a system database and effectively belongs to MS - yes you can put your own stuff in there at the risk of (1) breaking something or (2) having a service pack or hotfix break something for you...

Post #424850
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse