SQL Server Replication: Providing High Availability using Database Mirroring

  • Comments 4

Writer: Gopal Ashok (Microsoft Corporation), Paul S. Randal (SQLskills.com)

Technical Reviewers: Hilary Cotter (Relevant Noise), Prem Mehra, Lindsey Allen, Sanjay Mishra, Glenn Berry (SQL Server MVP), Jimmy May, Mike Ruthruff, Michael Redman, Joseph Sack, Jean-Yves Devant, Mike Weiner, and Mike Habben

Technical Writer: Glenn Minch

Project Editor: Diana Steinmetz

Originally Published: August 2008

Last Updated: March 2011

Applies to: SQL Server 2008, SQL Server 2008 R2

Summary: This white paper describes how to use database mirroring to increase the availability of the replication stream in a transactional environment. The document covers setting up replication in a mirrored environment, the effect of mirroring partnership state changes, and the effect of mirroring failovers on replication. In addition, it describes how to use LSN-based initialization to recover from the failover of a mirrored Subscriber database.

To download the entire paper please reference: http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/ReplicationAndDBM.docx

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Post
  • Pingback from  SQL Server Replication: Providing High Availability using Database Mirroring | Best Servers

  • Hi I am a beginner to SQL SERVER administraton which are the best books to learn

  • The paper suggests that when mirroring is failed over to the original partner ( ServerB) and the original principal (ServerA) is not available that "it is possible to easily make the Log Reader Agent continue to work by creating an alias for the original Publisher on the Distributor" i.e create an alias with the name "ServerA" that points to ServerB.

    I don't think we'd be the only people with legacy systems where the distributor is on the original principal. In which case this would create an alias for the instance's own name that points elsewhere. I haven't tested this yet, but I'm presuming it would be problematic.

    Am I correct in thinking that in this scenario we could change the "-Publisher" parameter for the call to the log reader agent from "ServerA" to "ServerB" and that this would have the same effect?

    Thanks,

    Paul

  • A Video tutorial on SQL Server Replication is posted Replication  which Answers, What is Replication ?, Components of Replication, How to Setup Snapshot, Transactional & Peer to Peer Replication.

    www.sqlserver-training.com/.../-

Page 1 of 1 (4 items)
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Post