Timeline for How to determine which statement is blocking an update in SQL Server
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2018 at 6:28 | answer | added | Learning_DBAdmin | timeline score: 0 | |
| Aug 8, 2018 at 21:17 | answer | added | Kin Shah | timeline score: 0 | |
| Aug 8, 2018 at 20:37 | answer | added | Clark Vera | timeline score: 0 | |
| Aug 8, 2018 at 16:11 | answer | added | Marques | timeline score: 0 | |
| Jan 6, 2015 at 13:22 | comment | added | RLF | No problem. I use this because the XML also (usually) shows where the block was in the blocked code and what the 'other' transaction was running. | |
| Jan 6, 2015 at 8:29 | comment | added | rghome | @RLF: I think the event notification is not useful as I already have detected the event (the application server complains about stuck threads), but this comment in the linked article is interesting: "Because you have the xactid you can track that down through SQL Profiler if you’d have been tracing SQLTransaction as well (another blog post on that I guess – the list get’s longer...)." I think that is what I want ... | |
| Jan 5, 2015 at 16:10 | comment | added | RLF | If you are interested in tracking blocking issues see Tony Rogerson's post at: sqlblogcasts.com/blogs/tonyrogerson/archive/2007/04/06/… | |
| Jan 5, 2015 at 16:08 | answer | added | Aaron Bertrand | timeline score: 7 | |
| Jan 5, 2015 at 15:58 | review | First posts | |||
| Jan 5, 2015 at 15:59 | |||||
| Jan 5, 2015 at 15:57 | history | asked | rghome | CC BY-SA 3.0 |