I currently have transactional replication set up for three databases from the same Publisher to the same three Subscribers in SQL Server 2005. Publisher and Distributor are on the same server.

One of the databases on one Subscriber stops for several hours each day at different times with no indication of why. No problem with all three databases on the other two Subscribers or the other two databases on the problem Subscriber.

Searching the system logs shows nothing abnormal happening on the Subscriber and Replication Monitor details just says "delivering replicated transactions". Inserting a tracer token shows the Publisher to Distributor is normal.

Any suggestions for troubleshooting this problem?

  • 1
    Any blocking going on ?
    – Kin Shah
    Commented Dec 14, 2018 at 19:22

1 Answer 1


Finally traced the issue to a table on the Subscriber that was missing the PK index. Still not too sure how this could have happened as all subscribers were initialized from the same snapshot at the same time. Re-initializing the individual subscriber had no affect. I had to; - remove the article from the publication - run the Snapshot Agent - manually drop the table on each Subscriber - add the article back to the publication - re-run the Snapshot Agent

All good now.

  • Sounds like a property mismatch on the article or metadata issue . Did you try scripting out the publication and looking at the settings for the article?
    – clifton_h
    Commented Dec 15, 2018 at 14:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.