May 8, 2003 at 10:29 pm
We got 3 SQL 2000 database servers, Master Server, 2 Standby Servers. If master server is down, our application will automatically switch to one of the standby servers and user could continue to update database. Once master server is up, application will switch back.
My problem is how to use replication to ensure all the 3 databases in sync?
Thanks for any advice.
======
Chris
May 9, 2003 at 7:56 am
Merge replication probably the easiest way.
Andy
May 9, 2003 at 11:23 am
Why not try Transactional replication with republishing topology..
May 11, 2003 at 8:50 pm
What you mean by republishing topology?
May 12, 2003 at 6:32 am
It is a replication when a publisher is also a susbcriber, and the subscribers are also publisher.
It is not the easiest schema, but it is the one I use here.
May 26, 2003 at 11:55 pm
quote:
It is a replication when a publisher is also a susbcriber, and the subscribers are also publisher.It is not the easiest schema, but it is the one I use here.
This sounds interesting. I have a system consisting of three servers. Master -> Staging -> Production. What I need is to be able to replicate from the master to the staging and then replicate from the staging to the production server.
Sort of a proofing concept. How does Republishing work within a SQL Server 2000 Environment? Any pointers? Can what I want done be done?
Thanks
Nick Gorst
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply