Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Use Transactional Replication and Database Mirroring at the same time


Use Transactional Replication and Database Mirroring at the same time

Author
Message
JJS.
JJS.
SSC Rookie
SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)

Group: General Forum Members
Points: 47 Visits: 153
Hi,

I have a setup transactional replication, the subscriber (pulled subscription) is used for reporting.
My problem is, I would like to setup Mirroring on the publisher DB to another server for failover.
Though it possible to use the subscriber as failover, but I find it tedious to implement (e.g., reseeding of identity column).

Is a good idea to mirror the publisher DB while it is used in transactional replication? Or is there a better approach?

Your comments and suggestions are highly appreciated.

Thanks.
steveb.
steveb.
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2848 Visits: 7195
You can mirror the publisher, you just need to esure that you are using a remote-distributor and that your agent is made fail-over aware

also you need to ensure that both the publisher and mirror-publisher can access the same snapshot folder.
gk-411903
gk-411903
SSC-Enthusiastic
SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)

Group: General Forum Members
Points: 169 Visits: 420
Please keep in mind that if something is not mirrored, then it will not be replicated ; Because in the case of a failover / switchover the new Principal cannot be ahead of the Replicated database. In other words , if the principal runs exposed then replication will lag behind.

HTH
gk
JJS.
JJS.
SSC Rookie
SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)

Group: General Forum Members
Points: 47 Visits: 153
Noted. I'll start exploring this in test environment.
Moreover, any suggested readings/links re best practices in managing databases both in replication and mirroring esp items that I need to watch out.

Again, Thanks in advance.
gk-411903
gk-411903
SSC-Enthusiastic
SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)SSC-Enthusiastic (169 reputation)

Group: General Forum Members
Points: 169 Visits: 420
Ok. Here are some links.

How to Perform Required Pre-Replication Setup Tasks
http://technet.microsoft.com/en-us/library/bb693465.aspx
**Hopefully you have not missed on setting the replication text size in the publisher**

Frequently Asked Questions for Replication Administrators
http://msdn.microsoft.com/en-us/library/ms151740.aspx
http://vyaskn.tripod.com/repl_ques.htm


Best Practices for Replication Administration
http://msdn.microsoft.com/en-us/library/ms151818.aspx


How to enable replication agents for logging to output files in SQL Server
http://support.microsoft.com/kb/312292


Strategies for Backing Up and Restoring Snapshot and Transactional Replication
http://msdn.microsoft.com/en-us/library/ms152560.aspx

** Make sure you configure the publishing db for sync_with_backup so that in case of db crash/restore you are 'saved' from the headache of 'break in continuity'; One downside to this is the possible increase in the log size@the publisher.**

Administration (Replication)
http://msdn.microsoft.com/en-us/library/ms152548.aspx


Monitoring (Replication)
http://msdn.microsoft.com/en-us/library/ms152751.aspx

HTH
gk(mct)
winash
winash
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1424 Visits: 1883
This document talks about replication and database mirroring (including information on trace flag 1448 which allows the log reader to replicate changes regardless of the mirroring state):

http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/ReplicationAndDBM.docx



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search