Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dim
Yak Posting Veteran
57 Posts |
 Posted - 2011-01-11 : 09:59:37
|
| Hi,I have a job that has 3 steps of run. The job runs successfully on some days and fails on most of the days. There is this deadlock which happens which leads to the job failure. On the day the job ran with successthe DBA'S got the alert notification on email "A process has been blocked for more than 300000 (ms)" . Is there a possible way to find out which process was blocked for more than 300000(ms)? Also is it possible to find out at which step and which query is causing the block ? I am new to the SQL server Job Agent would like to know the guidance/steps we need to follow in case of such situations?Thank you,dimDp |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-01-11 : 10:38:43
|
| when block is happening you can make use sp_who2 system procedure to understand which process is causing block. To see what that process is actually doing, use dbcc inputbuffer(<processid that caused blocking>)------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
|
|
|
SQL Server Job