Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/eleiba/i
well I don't wish to appear negative but checking for a lock that has been held for 5 to 10 mins might not be very efficient. I do a similar check periodically on our oltp systems but I check every 5 seconds for blocking locks.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
aba_lockinfo does a good job for this. Every 5 seconds is the best way as it was said above
We have servers that check every 30 seconds, and alerts us to blocking chains. However, our worst blockers are 3rd party apps that just block sometimes, nothing can be done, and the rocket scientist who purchased the app is long gone. We definitely don't want to be notified every 30 seconds! Our blocking notification process differs somewhat from what is in this article, but is pretty typical stuff that can be found on the web.
Viewing 4 posts - 1 through 3 (of 3 total)