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 |
|
schinni
Yak Posting Veteran
66 Posts |
 Posted - 2004-06-12 : 22:33:54
|
| My users are having some deadlock issues so i decided to run a traceso i found this data in the trace but i wanted to know if i am interpreting the data right and conveying back to the users.Here is how the data in the trace can any body explain how to interpret that.Event Class TextData spid ----------------------------------------------------------------------lock:deadlock chain Deadlock Chain SPID = 53Lock:deadlock chain Deadlock Chain Spid = 108Lock:Deadlock 108 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-12 : 23:17:41
|
| This doesn't do you a whole lot of good unless you captured what the SPID was doing at that time. You could capture with either Profiler (preferrable) or DBCC INPUTBUFFER(spid) (lucky).MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
schinni
Yak Posting Veteran
66 Posts |
Posted - 2004-06-12 : 23:45:26
|
| I have the sql that 53 and 108 spid are running but is 53 causing thedeadlock to 108 or the other way.Thanks, |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-13 : 12:51:55
|
| When you see that in Profiler, the 53 SPID was the "winner" of the deadlock. 108 was the loser. It's not really who caused what in the case of deadlocks. They both tried initiated events inside of a transaction that couldn't be resolved while maintaining atomicity, so one of the transactions was killed. What were the statements?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
Regarding Deadlock Issues