sql server replication: Using Replication for DR -- sql server replication

Using Replication for DR

Babooze1
9/18/2007 12:52:15 PM

sql server replication:

We plan to have two stand-alone servers (primary and failover) run MSSQL2000.
We want to use replication to keep the failover server up-to-date. When
something happens to the primary server, we switch the connections on the
application server to point to the failover server. The users should then be
able to continue their work.

My question is... What happens when we bring the primary server up. Will
it then propagate changes to the failover server? I don't want the failover
server with all the latest updates to be overwritten by the old data on the
primary server.

Re: Using Replication for DR

Hilary Cotter
9/18/2007 8:49:25 PM

For merge, bi-directional transactional, peer-to-peer, and transactional
with queued updating yes, on failover changes will be propagated back to the
publisher.

Replication is not recommend for DR as latencies can be unpredictable and
there is not automatic failover.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]