Timeline for SQL job get blocked after some time by a process on master DB
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 6 at 18:45 | review | Close votes | |||
Jan 24 at 3:04 | |||||
Jan 4 at 1:47 | comment | added | Charlieface |
What do you get from select * from sys.index_resumable_operations are there any rows? Are they PAUSED
|
|
Jan 3 at 22:27 | comment | added | siggemannen | What does dbcc inputbuffer(35) say? You are leaving out way too much details in your screenshots. In the last picture, it appears like some index is created automatically, since spid 35 is not a user process, perhaps you have some setting that creates these indexes? | |
Jan 3 at 7:49 | comment | added | Mohit Leekha | I have added the command, wait resource from sys.dm_exec_requests in the questions | |
Jan 3 at 7:48 | history | edited | Mohit Leekha | CC BY-SA 4.0 |
Added additional info
|
Jan 2 at 13:42 | comment | added | J.D. | What is the query of the blocking process?...does it read from your facts table? | |
Jan 2 at 13:36 | history | migrated | from stackoverflow.com (revisions) | ||
Jan 2 at 13:36 | comment | added | Charlieface | If it's sleeping then someone opened a transaction and forgot to commit or rollback. | |
Jan 2 at 13:27 | comment | added | siggemannen |
exec_sessions is meaningless to check, see sys.dm_exec_requests to see what kind of command it is etc
|
|
Jan 2 at 13:21 | history | asked | Mohit Leekha | CC BY-SA 4.0 |