Subscribe status showing Expire soon/Expired in transactinal replication

Ashutosh Mishra 1 Reputation point
2020-09-08T05:07:23.717+00:00

I am using SQL Serve Enterprise Edition (64-bit) and in this i am using transactional-replication with on Publisher , one Replication Distribution Agent with four Subscriber. everything was going smoothly but now when i am seeing my replication in SQL server through replication monitor and clicking on 'subscription watch list' all subscribers status are showing as 'Expiring soon/Expired' and i am not sure why and when i am double clicking on subscriber error message are 'no replicated transactions are available'.

SQL Server | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Shashank Singh 6,251 Reputation points
    2020-09-08T05:47:07.457+00:00

    This could mean that the articles from publisher has not reached subscriber and since threshold period is crossed they are marked as Expired or soon they may get expired. Please read the MS doc

    If a subscription is not synchronized within the maximum distribution retention period (default of 72 hours) and there are changes in the distribution database that have not been delivered to the Subscriber, the subscription will be marked deactivated by the Distribution clean up job that runs on the Distributor. The subscription must be reinitialized.

    Does replication monitor shows error? Are you able to send tracert tokens to all the subscribers ?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.