July 10, 2003 at 10:24 am
We have a scenario where our client application always connects to one database (A) and database (A) then connects to either database (B) or (C) depending upon the request. In addition database (B) and (C) can interact with each other also.
Now for failover and some other considerations we have deployed two SQL Servers both having the same setup. One of our requirements force us to take database (C) offline once a week (one server at a time) for data upload so the users have to switch from Primary Server to Secondary Server, which causes issues as database (B) of Secondary server is never as upto date as of Primary Server.
What I want to know is whether there is an easy way by which I can have only one database (B) to which databases (A) and (C) both can connect from either server and work, without a lot of code change in stored procedures and views.
Thanks for reading such a big description and your help.
Prateek.
~~~~~~~~
"Remember: 80% of bugs are just undocumented features waiting to be discovered!"
July 10, 2003 at 11:26 am
How big are these databases? Are there many schema changes?
If you say small and not many, then check out http://www.incepto.com/
Steve Jones
July 11, 2003 at 5:02 am
quote:
How big are these databases? Are there many schema changes?If you say small and not many, then check out http://www.incepto.com/
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
There are no schema changes and databases are small ... less than 2 GB each (B) and (C). (A) is just the interfacing database.. couple of MBs.
Prateek.
[HCL Technologies Ltd]
"Remember: 80% of bugs are just undocumented features waiting to be discovered!"
Prateek.
~~~~~~~~
"Remember: 80% of bugs are just undocumented features waiting to be discovered!"
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply