Transactional Replication Subscriber Database becomes in Recovery

  • I have setup transactional replication between 1 publisher and 2 subscribers.

    5 Databases are being replicated.

    Everything works well for a few weeks.

    Then, suddenly, I notice that a database in both subscribers become "In Recovery" (as shown in SSMS).

    The other 4 databases are still working without problem.

    The problematic database in both subscribers have been "In Recovery" for over 8-9 hours.

    Then one of them suddenly becomes available and replication becomes synchronized with publisher again.

    The other one (in the other subscriber) is still "In Recovery" until now.

    May I know how to diagnose this problem?

  • Found that the database was wrongly set to AUTO_CLOSE ON. Reset it to OFF seems fixed the problem.

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

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