June 22, 2012 at 7:57 am
We have server in production which is SQL SERVER 2008 R2 and acts as Publisher in Transactional Replication(It has two subscription and one Distributor) and at the same time it acts as principle in asynchronous mirroring.Yesterday as a test we suspended mirorring and we faced with latencies in subscriptions.It seems suspension had blocked the submission of transaction logs to Subscribers.Interesting point is the mirroring is asynchronous and not synchronous. Can suspended mirroring have effect on transactional replication?
June 22, 2012 at 8:03 am
What it will affect is that the transactions that need to go to the mirror database are queued until the mirror is resumed. This means the transactions are not cleared from the transaction log making each t-log backup larger. This could affect the movement of the t-log backups being shipped as they will take longer to be transferred and restored.
June 22, 2012 at 8:28 am
Thanks for your reply.
I had the same guess.But we also have log shipping set up on that machine and I noticed that the sizze of transaction logs backups have not changed and it has the around the same size as used to have.
June 23, 2012 at 2:50 pm
How much it changes depends on the activity of your server. If you haven't generated enough transactions to fill up the current virtual log file (VLF) and move on to the next, then you won't see any size difference in the log backups.
It won't cause latency on the subscriber. If you are experiencing latency, it is coincidental and not related to mirroring being suspended.
How many VLFs do you have? Run DBCC Loginfo in the database and tell us how many rows it returned. also, what is the total size and amount of free space in the log file?
One last thing. Where is the distribution database located? If on the same server a either the publisher or subscriber (or mirror), where are the database files located for it?
July 5, 2012 at 2:53 pm
The log reader agent will not read past transactions that have not been hardened on the mirror. Enabling trace flag 1448 will allow the server to continue delivering replicated transactions that have not been hardened on the mirror.
See the following KB article http://support.microsoft.com/kb/937041
August 11, 2012 at 6:20 am
Is there any impact to mirroring if transactional replication is broken for instance?
August 12, 2012 at 11:37 pm
Hi Kishore,
No, it will not impact to Mirroring.
Thanks
Satish
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply