SQL Replication issues

Question

Can anyone please suggest me, how to resolve below replication please

<stats state="2" fetch="105" wait="7474" cmds="1842373"

<stats state="2" fetch="105" wait="7474" cmds="1842373" callstogetreplcmds="1"><sincelaststats elapsedtime="300" fetch="5" wait="294" cmds="75492" cmdspersec="251.000000"/><message>Raised events that occur when an agent's reader thread waits longer than the agent's -messageinterval time. (By default, the time is 60 seconds.) If you notice State 2 events that are recorded for an agent, this indicates that the agent is taking a long time to write changes to the destination.</message></stats>

Answer 1

Hi Aella,

Do you see the subscriptions on the windows synchronization window?

Also, this may seem to indicate a timeout on the distribution instance. Have you observed resource bottlenecks? Not sure if the distribution instance in a local instance on subscriber or publisher or isolated from both, taking that transactional repl has been configured.

Feel free to browse the below catalog, which indeed aided me in troubleshooting replication issues. More specifically log reader latency

https://www.mssqltips.com/sql-server-tip-category/7/replication/

Regards,

M

Answer 2

Hi，Aella, Sreenivas

The following Introduction to the performance statistics tools for Replication Log Reader and Replication Distribution agents supplements the error message.

There are many causes for this delay, and you can find a solution by reviewing the agent logs.

These links provide some practical approaches for your reference：

https://www.mssqltips.com/sqlservertip/3598/troubleshooting-transactional-replication-latency-issues-in-sql-server/

https://techcommunity.microsoft.com/t5/sql-server-support-blog/effectively-troubleshoot-latency-in-sql-server-transactional/ba-p/4193429

Regards

Mikey Qiao

---

If you're satisfied with the answer, don't forget to "Accept it," as this will help others who have similar questions to yours.