Replication Subscriptions from SQL 2008 R2 server display Performance Critical

  • What I submitted to MS...

    Replication publications from SQL 2008 R2 box display Performance Critical message in Replication Monitor

    04/05/2013 08:17

    Subject:Replication publications from SQL 2008 R2 box display Performance Critical message in Replication Monitor

    Q: What is the issue? A: All of our publications from our new SQL 2008 R2 server display as Performance Critical. When the details are viewed for the subscriptions they display a non-responsive error message. Also all the subscriptions display the same Latency time.

    Q: What symptoms did you notice that led you to submit this support request? A: All the subscriptions from this SQL 2008 R2 box display performance errors. The other publication servers using the same distributor all display running as normal for their publications.

    Q: What is the exact text of any error messages that you received that are associated with this problem? A: The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.

    Q: What is occurring and what do you expect to be occurring? A: I would expect this publication server to run without issues like the others attached to the same distributor.

    Q: What system and version are you using when the problem occurs? A: The server we are having issues with is 2008 R2 OS and SQL 2008 R2. The distributor is 2008 R2 and SQL is 2012. Subscribers to the publications are all running 2008 OS with SQL 2008 server.

    Any help would be greatly appreciated!

    Thanks and Regards,

    Granny

    G. Chris Eickhoff 😎
    Senior Database Administrator

  • The error indicates that the Distributor agent is either processing a LOT of data or is hanging somewhere.

    What is the state of the connections from the Distributor agent at both the Distributor and the subscriber?

  • Try inserting a tracer token via the relication monitor to find where the issue is.. That should give you a good starting point on where to investigate the latency (pub - dist or dist - sub).

    Cheers

    Vultar

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply