SEa*_*986 5 sql-server deadlock locking sql-server-2016 deadlock-graph
我在我的系统上捕获了一个死锁，（匿名）XML 输出如下：
<deadlock>
<victim-list>
<victimProcess id="processf4d9233468" />
</victim-list>
<process-list>
<process id="processf4d9233468" taskpriority="0" logused="0" waitresource="KEY: 6:72057594039631872 (d117f90e375f)" waittime="481" ownerId="840005340" transactionname="SELECT" lasttranstarted="2019-10-14T10:16:07.550" XDES="0xeec803db90" lockMode="S" schedulerid="16" kpid="7220" status="suspended" spid="145" sbid="0" ecid="0" priority="0" trancount="0" lastbatchstarted="2019-10-14T10:16:07.547" lastbatchcompleted="2019-10-14T10:16:07.550" lastattention="1900-01-01T00:00:00.550" clientapp=".Net SqlClient Data Provider" hostname="MYWEBSERVER" hostpid="4512" loginname="MyOtherLogin" isolationlevel="read committed (2)" xactid="840005340" currentdb="6" currentdbname="MyDB" lockTimeout="4294967295" clientoption1="671088672" clientoption2="128056">
<executionStack>
<frame procname="MyDB.MySchema.MyProc" line="13" stmtstart="670" stmtend="9106" sqlhandle="MYSQLHANDLE">
SELECT p.[Col25]
, p.Col1
, pId.Col2
, p.Col3
, p.Col4
, p.Col5
, CONVERT(VARCHAR(10),p.Col6,103)
, a.[Col7]
, a.[Col8]
, a.[Col9]
, a.[Col10]
, a.[Col11]
, a.[Col12]
, a.[Col13]
, a.[Col14]
, a.[Col15]
, a.[Col16]
, a.[Col17]
, a.[Col18]
, a.[Col19]
FROM
(
SELECT COALESCE(p.[Col34], p.[Col25]) AS Col25
, lpm.[Col20]
, lpm.[Col21]
, ISNULL(c.[Col22] + ' ','') + ISNULL(c.[Col23] + ' ','') + ISNULL(c.[Col3],'')
, Table1.[Col10] AS [Col10]
, CONVERT(VARCHAR(10), ae.[Col23], 103) + ' ' + CONVERT(VARCHAR(5),ae.[Col23],108) AS Col11
, ISNULL(Table2.[Col24], ae.[Col25]) AS Col12
, ISNULL
</frame>
</executionStack>
<inputbuf>
Proc [Database Id = 6 Object Id = 279672044]
</inputbuf>
</process>
<process id="process103fec6f468" taskpriority="0" logused="292" waitresource="OBJECT: 6:2105058535:30 " waittime="1449" ownerId="840433263" transactionname="user_transaction" lasttranstarted="2019-10-14T10:16:42.233" XDES="0x103f9fb0e80" lockMode="IX" schedulerid="31" kpid="9972" status="suspended" spid="130" sbid="0" ecid="0" priority="0" trancount="2" lastbatchstarted="2019-10-14T10:16:42.240" lastbatchcompleted="2019-10-14T10:16:42.237" lastattention="1900-01-01T00:00:00.237" clientapp=".Net SqlClient Data Provider" hostname="MYWEBSERVER2" hostpid="3948" loginname="MyLogin" isolationlevel="read committed (2)" xactid="840433263" currentdb="6" currentdbname="MyDB" lockTimeout="4294967295" clientoption1="671088672" clientoption2="128056">
<executionStack>
<frame procname="adhoc" line="1" stmtstart="478" stmtend="1170" sqlhandle="0x020000006b742230b8276e1a3e7508dd257586243f5833450000000000000000000000000000000000000000">
unknown
</frame>
<frame procname="unknown" line="1" sqlhandle="0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000">
unknown
</frame>
</executionStack>
<inputbuf>
(@Col25 nvarchar(11),@Col26 nvarchar(11),@Col27 nvarchar(23),@Col28 nvarchar(12),@Col29 nvarchar(2),@Col30 nvarchar(4000),@Col23 nvarchar(23),@Col25 nvarchar(2),@Col31 nvarchar(11))
UPDATE [dbo].[TableInInputBuff]
SET [Col25] = @Col25,
[Col26] = @Col26,
[Col27] = @Col27,
[Col28] = @Col28,
[Col29] = @Col29,
[Col30] = @Col30,
[Col23] = @Col23,
[Col25] = @Col25
OUTPUT Inserted.Col31
WHERE [Col31]=@Col31
</inputbuf>
</process>
</process-list>
<resource-list>
<keylock hobtid="72057594039631872" dbid="6" objectname="MyDB.dbo.TableNotInInputBuff" indexname="PK__Encounte__4278DD362D27B809" id="lockf6be6aa900" mode="X" associatedObjectId="72057594039631872">
<owner-list>
<owner id="process103fec6f468" mode="X" />
</owner-list>
<waiter-list>
<waiter id="processf4d9233468" mode="S" requestType="wait" />
</waiter-list>
</keylock>
<objectlock lockPartition="30" objid="2105058535" subresource="FULL" dbid="6" objectname="MyDB.dbo.TableInInputBuff" id="lock10332f42500" mode="S" associatedObjectId="2105058535">
<owner-list>
<owner id="processf4d9233468" mode="S" />
</owner-list>
<waiter-list>
<waiter id="process103fec6f468" mode="IX" requestType="wait" />
</waiter-list>
</objectlock>
</resource-list>
</deadlock>
我可以看到幸存的进程 (spid130) 在一个表上有一个独占锁，该锁MyDB.dbo.TableNotInInputBuff
没有在<inputbuf>进程部分中显示的查询中使用process103fec6f468
我假设这里发生的事情是输入缓冲区仅显示来自较大事务的最后一条语句，并且该事务中的较早语句已完成更新或类似操作MyDB.dbo.TableNotInInputBuff，因此整个事务仍持有锁？
两个问题：
在某些情况下，可以对不是 UPDATE 直接目标的表（例如外键或更新触发器）进行锁定，但我认为这里不是这种情况？
当然，时间戳显示在同一事务中存在前一批
因此，锁定可能已被16:42.233和之间的另一个批次占用16:42.237。
没有任何内置功能可以帮助您解决此问题。SQL Server 不会保留先前执行的 SQL 文本的此历史记录，只是因为会话可能会在以后的批处理中陷入死锁。
最好的方法是审计应用程序代码以查看它在同一事务中较早提交的其他语句。如果这是不可能的，您将需要查看扩展事件以在应用程序运行该代码路径时捕获来自应用程序的所有语句。