Database Reference
In-Depth Information
■
Do not use client side traces with SQl profiler application in the production environment. Client side traces
degrade server performance and consume a significant amount of network bandwidth. use server side traces instead.
Note
The blocked process report contains XML that shows information about blocking and blocked processes in the
system (the most important of which are highlighted in boldface within Listing 18-4).
Listing 18-4.
Blocked Process Report XML
<blocked-process-report monitorLoop="224">
<blocked-process>
<process id="process3e576c928" taskpriority="0" logused="0"
waitresource="KEY:
11:72057594039500800 (5be201b53ff8)
"
waittime="14102
" ownerId="..." transactionname="SELECT"
lasttranstarted="..." XDES="..."
lockMode="S"
schedulerid="1" kpid="..." status="suspended"
spid="53"
sbid="0" ecid="0" priority="0" trancount="0" lastbatchstarted="..."
lastbatchcompleted="..." lastattention="..." clientapp="..." hostname="..." hostpid="..."
loginname="..."
isolationlevel="read committed (2)"
xactid="..." currentdb="14" lockTimeout="..."
clientoption1="..." clientoption2="...">
<executionStack>
<frame line="3" stmtstart="46" sqlhandle="..."/>
<frame line="3" stmtstart="100" sqlhandle="..."/>
</executionStack>
<inputbuf>
set transaction isolation level read committed
select OrderId, Amount
from Delivery.Orders
where OrderNum = '950'
</inputbuf>
</process>
</blocked-process>
<blocking-process>
<
process status="sleeping" spid="54"
sbid="0" ecid="0" priority="0"
trancount="1"
lastbatchstarted="..." lastbatchcompleted="..." lastattention="..." clientapp="..." hostname="..."
hostpid="..." loginname="..."
isolationlevel="read uncommitted (1)"
xactid="..." currentdb="14"
lockTimeout="..." clientoption1="..." clientoption2="...">
<executionStack/>
<inputbuf>
set transaction isolation level read uncommitted
begin tran
delete from Delivery.Orders
where OrderId = 95
</inputbuf>
</process>
</blocking-process>
</blocked-process-report>
