Re: calling Stored Procedures from different DBs
From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 03/24/04
- Next message: John Hoge: "Sproc with temp tables and input parameters causing trouble with dynamic recordsets - a tricky one!"
- Previous message: MikeL: "SELECT * FROM (exec mystoredproc) as table1"
- In reply to: ZeBerg: "calling Stored Procedures from different DBs"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 07:38:24 -0600
We keep all of our DDL scripts under source control. It's a simple task to
promote these to as many databases as needed.
-- Hope this helps. Dan Guzman SQL Server MVP "ZeBerg" <anonymous@discussions.microsoft.com> wrote in message news:4191EC3A-FA7F-4910-8766-1DA8E2C62106@microsoft.com... > Is it possible to have a stored procedure in database A while calling it from database B and have it manipulate the tables in database B (whatever the calling database happens to be)? > > We have a large-scale app that uses many complex stored procedures, and as of now, we're copying the SPs to every new database that is created, and it will soon become a nightmare for propagating updates and fixes. We'd like to keep a master set of the SPs in one DB and "use" them from other DBs so that they only query data and manipulate tables in the calling DB. I hope someone has some suggestions. Thanks.
- Next message: John Hoge: "Sproc with temp tables and input parameters causing trouble with dynamic recordsets - a tricky one!"
- Previous message: MikeL: "SELECT * FROM (exec mystoredproc) as table1"
- In reply to: ZeBerg: "calling Stored Procedures from different DBs"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
