Switching Over to a Warm Standby (Subscriber)

If done properly, failing over to a warm standby (subscriber) in a replication configuration can be done in less than two minutes if the failure is detected early. There will be a few main areas to consider:

  • Knowing what has failed. Has the publisher failed only? Have the most recent transactions been replicated to the subscriber?

  • Define the process that must be run to make the subscriber the primary server.

  • Define the process that must be followed to point the client to the new primary server (the standby).

  • Define the process to switch this all back to the way it was before the failure occurred (if desired).

Just as a precaution, you should always keep all the SQL Server instances that are a part of ...

Get Microsoft® SQL Server High Availability now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.