October 5, 2010 at 8:13 am
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.
October 5, 2010 at 8:35 am
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.
October 13, 2010 at 6:07 pm
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
October 14, 2010 at 8:31 am
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.
October 14, 2010 at 10:57 am
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)
October 14, 2010 at 11:20 am
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):
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply