Groups | Blog | Home
all groups > sql server replication > may 2006 >

sql server replication : Upgrading HA Applications with Replication


burtwalker
5/20/2006 7:24:52 AM
We're in the process of setting up a high availability system in two
separate geographic locations using SQL Server 2000. One will be used
as primary production site, the other replicated to be used in two
ways: 1) hot backup site in the event 1st site is unavailable, and 2)
for purposes of acting as primary when original primary is being used
for data extraction and table updates. If I'm not mistaken, this would
require merge replication.

How would we get the replicated sites synchronized if we need to make
any changes to database structure, upgrades, bug fixes, etc?
Hilary Cotter
5/20/2006 1:02:48 PM
You should use bi-directional transactional replication. If you choose to
use it, you would drop the subscriptions, make the changes using
sp_repladdcolumn and sp_repldropcolumn, and then regenerate the replication
stored procedures, recreate the subscriptions using no-sync, and start up
the agents.

You have more options in SQL 2005.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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]

Paul Ibison
5/22/2006 12:00:00 AM
I'd look at the following in BOL: bidirectional transactional replication,
queued updating subscribers, log shipping and database mirroring (SQL 2005).
They each have their own quirks and advantages, but FWIW I tend to use
queued updating subscribers where possible for replication HA.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

AddThis Social Bookmark Button