Click here to Skip to main content
15,885,014 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Like an alert created that tracks replication subscription application processing time (how long it tables the actual queries that insert/update records). I want to know the duration if it last longer than 15 seconds and I want to know if those long running spids are blocking anything else during that time (number of blocked spids)

I know the regular blocking alert does some of this work, but I want to focus specifically on replication SPIDs. Right now this is primarly just information collection to focus performance tuning efforts, which may eventually morph into an alert. Ultimately, we want to avoid replication blocking taking down.

Also would like to know as we have lot of blocking issues and most of the times it was due to replication so how can we identity replication blocking processes and along with Distributor:Subscriber Latency(I have below script to check Latency either on Publisher to Distributor or Dist: to Subscriber.
-->
SELECT SUM(cntr_value)/1000/60 as ReplicationLatencyInMinutes FROM sys.dm_os_performance_counters (nolock)
WHERE counter_name in ('Dist:Delivery Latency','Logreader:Delivery Latency');
Posted
Updated 11-Jun-15 1:22am
v3
Comments
_Asif_ 11-Jun-15 8:13am    
This sounds interesting. Check please http://dba.stackexchange.com/questions/88923/replication-monitor-information-using-t-sql

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900