Re: Use of "USE databasename" Within a Stored Procedure
- From: Hugo Kornelis <hugo@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 Dec 2005 00:34:23 +0100
On Wed, 7 Dec 2005 07:39:02 -0800, RitaG wrote:
>Hi Hugo,
>
>Thanks for your response.
>
>We do data loads for different companies and each company has it's own SQL
>database within the same SQL server.The logic and stored procedures for each
>company's data load is different so it has not been an issue before. We now
>have taken on the task of 30 more data loads but they all use the same logic
>and stored procedures. Rather than duplicate the logic 30 times in each of
>the databases I wanted 1 common place where all the logic and stored
>procedures for these 30 data loads reside and all 30 move through this common
>place but load the data into their separate databases. We have a whole system
>designed around these separate databases and so I cannot put everything into
>just 1 database for these 30.
Hi Rita,
In this case, using seperate databases might be the better option.
Companies that happen to use the same table structure and procedures now
will probably start to diverge at a later time.
I would therefor also recommend copying the stored proc in all 30
databases. It's a bit more work now, but that will pay itself back later
when some of these companies want to tweak their DB and others don't.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)
.
- References:
- Re: Use of "USE databasename" Within a Stored Procedure
- From: Hugo Kornelis
- Re: Use of "USE databasename" Within a Stored Procedure
- Prev by Date: Re: Use of "USE databasename" Within a Stored Procedure
- Next by Date: Re: Use of "USE databasename" Within a Stored Procedure
- Previous by thread: Re: Use of "USE databasename" Within a Stored Procedure
- Next by thread: Re: Use of "USE databasename" Within a Stored Procedure
- Index(es):
Relevant Pages
|
|