Stored Procedure & 'other' database

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » Stored Procedure & 'other' database

13 posts, Page 2 of 2

««1 2

Stored Procedure & 'other' database

Rate Topic

Display Mode

Topic Options

Author

Message

Michael Earl-395764

Posted Wednesday, November 21, 2007 6:51 AM

SSCrazy

Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,732, 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

r.vanlaake

Posted Wednesday, November 21, 2007 6:58 AM

Forum 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

Joe Clifford

Posted Thursday, November 22, 2007 12:35 AM

SSC-Addicted

Group: General Forum Members
Last Login: Monday, January 07, 2013 11:28 PM
Points: 433, Visits: 618

"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 »

13 posts, Page 2 of 2

««1 2

Permissions