Options
Receiving alerts about blocking/deadlocks too late
sql_guy75
Posts: 5
We had a blocking occurred in our environment supposedly around 11:11 AM yesterday on 4/2/2014. However, within the alert inbox, we do not see that there is a blocking occurring, not until at 2:00 am the next day on 4/2 2:00, which it then starting reporting it, because another process tried to access the SQL resources.
I can see that there is a long query reported at 11:13, but supposedly it ended since it reported the completed duration.
The first alert I received, which was around 2:00 AM is when the import process runs. The alert indicates that blocking process/query started at 11:11 am on 2 Apr 2014.
I would nice to be alerted of this symptom before it becomes a problem, as it did last night.
I can see that there is a long query reported at 11:13, but supposedly it ended since it reported the completed duration.
The first alert I received, which was around 2:00 AM is when the import process runs. The alert indicates that blocking process/query started at 11:11 am on 2 Apr 2014.
I would nice to be alerted of this symptom before it becomes a problem, as it did last night.
Comments