Difference Between “Long merge” and “Slow merge” Replication Warnings

<div><div align="left"> During my presentation about Transactional Replication at <a href="http://www.sqlsaturday.com/" target="_blank">SQLSaturday</a> #8 last weekend I was asked what the difference was between “Long merge” and “Slow merge” replication warnings. I didn’t know the answer (it was a session about transactional replication after all), but not being one to let a good question go unanswered I had to find out. </div> Here’s what they mean:<br/> <ul> <li><strong>Long merge</strong> refers to the amount of time that the merge agent has run (or is currently running) during the most recent synchronization. If this value exceeds the set threshold the alert will fire. </li> <li><strong>Slow merge</strong> refers to the number of rows processed per second by the merge agent while running. If this value falls below the set threshold the alert will fire. </li> </ul> There are two threshold values for each alert - one for dialup connections and one for LAN connections. For dialup the default is 8 minutes for long merge and 20 rows/sec for slow merge. For LAN the default is 3 minutes for long merge and 100 rows/sec for slow merge. <br/> Thresholds are enabled and set in Replication Monitor by selecting your merge publication in the left pane and the “Warnings” tab in the right pane. Alert actions are set by clicking the "Configure Alerts…” button in the same pane or in Management Studio's Object Explorer under SQL Server Agent -> Alerts. A screenshot of the Warnings tab in Replication Monitor is below.<br/> <p align="center" style="text-align: center;"><img align="center" border="0" height="339" src="../../-l0lqRpiUf-4/SQYt3Pcl3FI/AAAAAAAAATA/v0gQHjvu3e4/s800/image-5B15-5D.jpg" width="633"/></p> </div>

Share This

• Twitter
• Google+
• Linked In
• Facebook

Related Posts

Replication SQLSaturday