Hi All,We encountered a strange replication issue. Our client told us that the subscriber database is not up to date. Thus we checked to verify if there is any latency. We found about 3 hour latency. We waited for some time to see if we can find any improvement but it didn't change. Thus we restarted logreader replication job and replication came back to sync in about 5 minutes.We are trying to find root cause of this issue. As I mentioned the resolution was just to restart replication job and it came back to sync. But not sure why it didn't sync itself because replication job was already running. Did you encounter this similar issue? If yes what was the root cause?Thanks.
↧