Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Replication for warm standby
0 views
Skip to first unread message
Raimol John
May 1, 2003, 11:29:47 AM5/1/03
to
We are planning to use replication between sql 2000
servers for a warm standby. Are there any set procedures
to follow in case of a failover and failback scenario. We
have tables that have identity columns ( these would be
created with the 'NOT FOR REPLICATION' option at the
subscriber) and triggers that need to be disabled at the
subscriber. In the case of a failover, do we have to turn
off 'NOT FOR REPLICATION' at the subscriber(the warm
standby) and turn it on at the publisher when the warm
standby have to taken over as the primary server.
servers for a warm standby. Are there any set procedures
to follow in case of a failover and failback scenario. We
have tables that have identity columns ( these would be
created with the 'NOT FOR REPLICATION' option at the
subscriber) and triggers that need to be disabled at the
subscriber. In the case of a failover, do we have to turn
off 'NOT FOR REPLICATION' at the subscriber(the warm
standby) and turn it on at the publisher when the warm
standby have to taken over as the primary server.
Are there any set procedures to follow in case of a
failover and failback scenario. Any advice ???
TomHirt
May 1, 2003, 3:27:26 PM5/1/03
to
You really need to ask yourself if replication is your
solution. I went that route and had major heartburn
working around the Identity columns/Identity Seed
problem. If you are trying to create a Warm Stand-By
server, go with Log Shipping! Here's a great link:
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com/support/sql/content/2000p
apers/LogShippingFinal.asp
solution. I went that route and had major heartburn
working around the Identity columns/Identity Seed
problem. If you are trying to create a Warm Stand-By
server, go with Log Shipping! Here's a great link:
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com/support/sql/content/2000p
apers/LogShippingFinal.asp
Note the last pages talking about the Clustering,
Replication, and Log Shipping solutions. Hope this
helps. Now we just need to start a Log Shipping
newsgroup! :)
>.
>
Raimol John
May 2, 2003, 8:16:47 AM5/2/03
to
Thank you so much for your input. We already have log
shipping in place and were looking for more real-time
replication as a solution for warm standby. Thanks again.
shipping in place and were looking for more real-time
replication as a solution for warm standby. Thanks again.
Rachan Terrell
May 5, 2003, 1:40:22 PM5/5/03
to
John,
Here is a link that will help you:
http://vyaskn.tripod.com/maintaining_standby_sql_server.htm
Good Luck,
Rachan
>.
>
Rachan Terrell
May 5, 2003, 1:40:22 PM5/5/03
to
John,
Here is a link that will help you:
http://vyaskn.tripod.com/maintaining_standby_sql_server.htm
Good Luck,
Rachan
>.
>
0 new messages