Transactional Replication

• Admingod

  SSCertifiable

  Points: 5997

  More actions

  January 25, 2019 at 9:42 am

  #376874

  I got the below alerts from Transnational Replication about Latency. My understanding is that these are warnings cause when the replication was running delay due to some other process interfering right? However,  I don't see these warnings any more. Does it mean that replication are cough up now and alerts are not triggering? Let me know if i am missing anything here or i need to troubleshoot further. Please advise? 

  SQL Server Alert System: 'Replication Warning: Transactional replication latency (Threshold: latency)' occurred

  Thanks

• Sue_H

  SSC Guru

  Points: 90860

  More actions

  January 25, 2019 at 10:47 am

  #2020148

  Admingod - Friday, January 25, 2019 9:42 AM

  I got the below alerts from Transnational Replication about Latency. My understanding is that these are warnings cause when the replication was running delay due to some other process interfering right? However,  I don't see these warnings any more. Does it mean that replication are cough up now and alerts are not triggering? Let me know if i am missing anything here or i need to troubleshoot further. Please advise? 

  SQL Server Alert System: 'Replication Warning: Transactional replication latency (Threshold: latency)' occurred

  Thanks

  If you aren't seeing the alerts then replication is caught up. It does fire when the latency exceeds the value you set (I think 30 secs is the default). Check the performance column in replication monitor when viewing the subscriptions. It would have a warning if you are still having problems.
  You can view the alert settings from replication monitor, select a subscription on the left pane and then click on the warnings tab on the right.

  Sue

• Admingod

  SSCertifiable

  Points: 5997

  More actions

  January 25, 2019 at 10:54 am

  #2020149

  Thanks Sue! I see the performance is Excellent right now. However, i checked the warning threshold which is default 30 secs. Does it mean replication is running 30 secs behind during the alerts? Do you thing i should change default value 30 secs or it should be fine?

• Sue_H

  SSC Guru

  Points: 90860

  More actions

  January 25, 2019 at 11:06 am

  #2020150

  Admingod - Friday, January 25, 2019 10:54 AM

  Thanks Sue! I see the performance is Excellent right now. However, i checked the warning threshold which is default 30 secs. Does it mean replication is running 30 secs behind during the alerts? Do you thing i should change default value 30 secs or it should be fine?

  Great - so your replication is running fine now!
  The 30 seconds on the latency is for if the transactions are taking over 30 seconds to get from the publisher to the subscriber. 30 seconds is generally fine for most.
  You will typically get some alerts at this setting but it's usually during maintenance, loads to the publisher and things like that. If you get some during those times and then replication catches up, you can ignore those. If the replicated database is meeting business needs and requirements with the current setting, I wouldn't worry about it.

  Sue