Timeline for Blocked Process Report -two updates causing a long block
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2015 at 9:10 | comment | added | user3585420 | Hello, I have done this. The operations which causes the blocking is the UPDATE that I originally show in my question. You can see the execution plan for this UPDATE in my comments for the first Answer by @armitage | |
| Jun 15, 2015 at 20:33 | comment | added | Ionic | Normally, yes. You can then compare which operations run and what part of the operation could cause the block. | |
| Jun 15, 2015 at 14:32 | comment | added | user3585420 | Ok, I'm running the tsql replay template now on the database, what is it that I'm looking out for, do I have to wait for the blocked process report to happen and then marry up the times of the event? | |
| Jun 15, 2015 at 13:52 | comment | added | Ionic | Because you don't know why they are blocking/deadlocking each other? | |
| Jun 15, 2015 at 13:48 | comment | added | user3585420 | Hello, thanks for your comments. I don't understand why any of the suggestions in the comments / answer are helpful. I already know what query is causing the blocking right? So I don't need to do any further trace? Or have I got that wrong? | |
| Jun 15, 2015 at 13:40 | comment | added | Ionic | Yes but you don't have to configure it manually. Normally you configure it using profiler. Configure it to write it to a table or file. Start it, pause it. Close profiler and start it using standard sql. Therefore no results were send to your client. | |
| Jun 15, 2015 at 13:38 | comment | added | Kin Shah |
But you can capture workload using profiler on the prod server and rerun it on the test system. NO, as I said, a server side trace or XEvent is much lighter.
|
|
| Jun 15, 2015 at 13:35 | comment | added | Ionic | Well not in prod, but normally you have an test instance as well. But you can capture workload using profiler on the prod server and rerun it on the test system. Well I would like to comment on the OP's question. But due to the bad reputation system in stackexchange, I won't be able to comment unless I have a reputation of 50. | |
| Jun 15, 2015 at 13:29 | comment | added | Kin Shah | I would recommend NOT running profiler in PROD. A server side trace or XEvents would be a much better choice. Also, your answer does not really provide answer to OP's question, since the blocked process report already has lock information in it. | |
| Jun 15, 2015 at 13:22 | history | answered | Ionic | CC BY-SA 3.0 |