Causes and Solutions for Deadlocks - SQL Server Query Performance Tuning - page 441

Table 21-1. ( continued )

Entry in Log Description

<inputbuf>
UPDATE Purchasing.PurchaseOrderDetail
SET OrderQty = 4
WHERE ProductID = 448
AND PurchaseOrderID = 1255 ; </inputbuf>

The statements for the current batch. This is
followed by the query showing the precise
values used by the statement defined earlier.
They were substituted as parameters as simple
parameterization.

<process id="processf4ecf498" taskpriority="0"
logused="10896" waitresource="KEY:
9:72057594046840832 (4bc08edebc6b)" waittime="7851"
ownerId="21222" transactionname="user_transaction"
lasttranstarted="2012-01-18T17:42:05.957"
XDES="0xf682cd28" lockMode="U" schedulerid="2"
kpid="4944" status="suspended" spid="55"
sbid="0" ecid="0" priority="0" trancount="2"
lastbatchstarted="2012-01-18T17:42:05.957"
lastbatchcompleted="2012-01-18T17:42:05.957"
lastattention="1900-01-01T00:00:00.957"
clientapp="Microsoft SQL Server Management
Studio - Query" hostname="DOJO" hostpid="2376"
loginname="NEVERNEVER\grant" isolationlevel="read
committed (2)" xactid="21222" currentdb="9"
lockTimeout="4294967295" clientoption1="673327200"
clientoption2="390200">

The next process in the deadlock. In this case, this is
the process that succeeded. Sometimes you can see
a different order in the output of the graph.

<executionStack>
<frame procname=" AdventureWorks2008R2.Purchasing.
uPurchaseOrderDetail " line="39" stmtstart="2732"
stmtend="3864" sqlhandle="0x0300090076146e6c1
6a11f01c69d0000000000000000000 000000000000000000000
00000000000000000000">
UPDATE [Purchasing].[PurchaseOrderHeader]
SET [Purchasing].[PurchaseOrderHeader].[SubTotal] =
(SELECT SUM([Purchasing].[PurchaseOrderDetail].
[LineTotal])
FROM [Purchasing].[PurchaseOrderDetail]
WHERE [Purchasing].[PurchaseOrderHeader].
[PurchaseOrderID]
= [Purchasing].[PurchaseOrderDetail].
[PurchaseOrderID])
WHERE [Purchasing].[PurchaseOrderHeader].
[PurchaseOrderID]
IN (SELECT inserted.[PurchaseOrderID] FROM
inserted); </frame>

Note the procname value, AdventureWorks2008R2.
Purchasing.uPurchaseOrderDetail .
This is a trigger fired and running the following code.

( continued )