|
Home > Archive > microsoft.public.sqlserver.server > November 2002 > Need suggestions for handling multiple databases between development/production
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Need suggestions for handling multiple databases between development/production
|
|
| Christopher Klein 2002-11-26, 11:23 am |
| Greetings,
Relatively new to database management and I find myself with something of an
issue that I'm hoping someone else can give me a handle on.
We currently have two development databases for two products that get
installed at client sites (Called Database_A and Database_B for example)
The client sites also use the same naming of Database_A and Database_B and
everything from the individual clientsides work fine.
The problem is that by the nature of our business we need to maintain a copy
of the client's database in house so we've gotten into the habit of bringing
them back in-house and giving them different names like Town1_A and Town1_B.
Under some circumstances we have used sql that spans the two databases, as
they are defined on site of Database_A and Database_B. Is there a good way
to switch in and out databases when we WANT to just check out information
from Town1_A and Town1_B?
I'm thinking that it almost has to be a manual process. That we should get
another server JUST for the client databases, and restore the town that we
want to be working with WHEN we need it.
Any thoughts would be appreciated
Christopher Klein
| |
| Tibor Karaszi 2002-11-29, 2:23 am |
| Not sure exactly what the problem is, but can you restore all client databases under different
names and then swap names using sp_renamedb perhaps?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ublic.sqlserver
"Christopher Klein" <nospam-cklein5@attbi.com> wrote in message
news:OaRfJsWlCHA.2020@tkmsftngp02...
> Greetings,
>
> Relatively new to database management and I find myself with something of an
> issue that I'm hoping someone else can give me a handle on.
>
> We currently have two development databases for two products that get
> installed at client sites (Called Database_A and Database_B for example)
> The client sites also use the same naming of Database_A and Database_B and
> everything from the individual clientsides work fine.
>
> The problem is that by the nature of our business we need to maintain a copy
> of the client's database in house so we've gotten into the habit of bringing
> them back in-house and giving them different names like Town1_A and Town1_B.
> Under some circumstances we have used sql that spans the two databases, as
> they are defined on site of Database_A and Database_B. Is there a good way
> to switch in and out databases when we WANT to just check out information
> from Town1_A and Town1_B?
>
> I'm thinking that it almost has to be a manual process. That we should get
> another server JUST for the client databases, and restore the town that we
> want to be working with WHEN we need it.
>
> Any thoughts would be appreciated
>
> Christopher Klein
>
>
|
|
|
|
|