I have a couple questions about this. I am using SQL Server 2014. The database that has problems is less the 100 MB. I will get how busy the server is later.
Background. I am helping someone identify the source of intermittent timeouts. My understanding is that their .Net applications are running fine most of the time. But then the application begins timing out. I haven't established yet whether this is a connection time out or whether the query times out (that will come later). I am toying with the following approach.
I create an alert on Lock:Lock Timeouts (timeout > 0)/sect on instance _total, if counter > 0.
The response is to run a job that runs a script that will dump the current connections, their waiting status, whether they are head blocker, etc (I can build this) into a table.
Next for Options, I want to set the Delay between responses to 4 minutes.
Questions:
1) What performance issues can I anticipate? Is there no risk, moderate risk or high risk of this alert causing performance problems in a scenario of moderate work load, high work load (100 transactions per second, a number I pulled out of my hat).
2) My second question I think that I can test. But off the top of your head, does an ADO.Net command cause a timeout that this alert can listen to.
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com