Secondary server - Best practice
From: Paul Ibison (Paul.Ibison_at_Pygmalion.Com)
Date: 02/28/05
- Next message: Paul Ibison: "Error at parameter 1 during datastream processing of parameterized"
- Previous message: Paul Ibison: "Re: Recommended Practices for Duplicating Data Across Multiple Ser"
- In reply to: Jorge Martinez: "Secondary server - Best practice"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 28 Feb 2005 07:51:39 -0800
This article might help a bit:
http://www.replicationanswers.com/Standby.htm
For bidirectional replication there are several options:
merge, transactional with updating subscribers and
snapshot with upd subscribers. I would recommend
transactional with queued updating subscribers for your
scenario. It copes well with identity columns, won't
change the table schema, and to reverse the changes when
the production box is later available, you can run the
queue reader agent.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
- Next message: Paul Ibison: "Error at parameter 1 during datastream processing of parameterized"
- Previous message: Paul Ibison: "Re: Recommended Practices for Duplicating Data Across Multiple Ser"
- In reply to: Jorge Martinez: "Secondary server - Best practice"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
