all groups > sql server replication > january 2007 >
You're in the

sql server replication

group:

best solutions : sql server replication (Maintenance)


best solutions : sql server replication (Maintenance) DKRReddy
1/4/2007 10:56:13 PM
sql server replication:
we are frequently running the maintenance tasks on production during that
databases are not accessible.
to avoid this we want to switch over to the standby server during maintenace
and after maintenance has been completed
switch back to primary server.During maintenance all data changes need to be
replicated back to production server.

To accomplish this I am planning to setup database replication from
producation database server to Standby server.
Please advise best solutions for this like microsoft trnsaction
replication,Goldengate replication, wansync replication.

I think microsoft trnsaction replication,Goldengate replication doesn't
support complex shema changes to get replicated.

Requirement :
1. 10 databases need to get replicated (with 30GB - 70GB each)
2. these 10 databases will have schema changes monthly.
3. data changes need to moved from standby to production server after
maintenance has been completed.

Please advise
Thanks

Re: best solutions : sql server replication (Maintenance) Hilary Cotter
1/5/2007 7:36:49 AM
I think bi-directional transactional replication is ideal for this. Point
the feed to the standby when you want to do maintenance on the primary. Then
stop the distribution agents, do your work, and restart the agents, and then
repoint to the primary.

When you do your schema changes you will have to tear down replication on
both sides and recreate it after you have done the schema changes.
--
Hilary Cotter

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]

AddThis Social Bookmark Button