Question

请帮我分析死锁，在那里我看到这两个更新存储过程相互死锁。我无法弄清楚他们互相锁定的内容，以及解决死锁问题的原因：

2011-05-19 14:00:15.610 spid23s      Deadlock encountered .... Printing deadlock information
2011-05-19 14:00:15.610 spid23s      Wait-for graph
2011-05-19 14:00:15.610 spid23s      NULL
2011-05-19 14:00:15.610 spid23s      Node:1
2011-05-19 14:00:15.610 spid23s      PAGE: 28:1:17381               CleanCnt:3 Mode:U Flags: 0x3
2011-05-19 14:00:15.610 spid23s       Grant List 2:
2011-05-19 14:00:15.610 spid23s         Owner:0x000000013A3EE1C0 Mode: U        Flg:0x40 Ref:0 Life:00000001 SPID:238 ECID:0 XactLockInfo: 0x00000002B04199B0
2011-05-19 14:00:15.610 spid23s         SPID: 238 ECID: 0 Statement Type: UPDATE Line #: 18
2011-05-19 14:00:15.610 spid23s         Input Buf: RPC Event: Proc [Database Id = 28 Object Id = 1531152500]
2011-05-19 14:00:15.610 spid23s      Requested by: 
2011-05-19 14:00:15.610 spid23s        ResType:LockOwner Stype:'OR'Xdes:0x000000039F83AE90 Mode: U SPID:215 BatchID:0 ECID:0 TaskProxy:(0x00000002A9A8E538) Value:0xd45ccfc0 Cost:(0/0)
2011-05-19 14:00:15.610 spid23s      NULL
2011-05-19 14:00:15.610 spid23s      Node:2
2011-05-19 14:00:15.610 spid23s      PAGE: 28:1:26081               CleanCnt:2 Mode:U Flags: 0x3
2011-05-19 14:00:15.610 spid23s       Grant List 3:
2011-05-19 14:00:15.610 spid23s         Owner:0x000000043091B9C0 Mode: U        Flg:0x40 Ref:0 Life:00000001 SPID:284 ECID:0 XactLockInfo: 0x000000051D4E1D30
2011-05-19 14:00:15.610 spid23s         SPID: 284 ECID: 0 Statement Type: UPDATE Line #: 9
2011-05-19 14:00:15.610 spid23s         Input Buf: Language Event: up_BulkMailSchedule_ResetStuckItems
2011-05-19 14:00:15.610 spid23s      Requested by: 
2011-05-19 14:00:15.610 spid23s        ResType:LockOwner Stype:'OR'Xdes:0x00000002B0419970 Mode: U SPID:238 BatchID:0 ECID:0 TaskProxy:(0x0000000282C9C538) Value:0xd5770500 Cost:(0/0)
2011-05-19 14:00:15.610 spid23s      NULL
2011-05-19 14:00:15.610 spid23s      Node:3
2011-05-19 14:00:15.610 spid23s      PAGE: 28:1:17381               CleanCnt:3 Mode:U Flags: 0x3
2011-05-19 14:00:15.610 spid23s       Wait List:
2011-05-19 14:00:15.610 spid23s         Owner:0x00000004D45CCFC0 Mode: U        Flg:0x42 Ref:1 Life:00000001 SPID:215 ECID:0 XactLockInfo: 0x000000039F83AED0
2011-05-19 14:00:15.610 spid23s         SPID: 215 ECID: 0 Statement Type: UPDATE Line #: 18
2011-05-19 14:00:15.610 spid23s         Input Buf: RPC Event: Proc [Database Id = 28 Object Id = 1531152500]
2011-05-19 14:00:15.610 spid23s      Requested by: 
2011-05-19 14:00:15.610 spid23s        ResType:LockOwner Stype:'OR'Xdes:0x00000002F346DC60 Mode: U SPID:284 BatchID:0 ECID:1 TaskProxy:(0x00000002E1989360) Value:0xce7f3b00 Cost:(0/0)
2011-05-19 14:00:15.610 spid23s      NULL
2011-05-19 14:00:15.610 spid23s      Node:4
2011-05-19 14:00:15.610 spid23s      Port: 0x00000002E3150380  Xid Slot: 0, Wait Slot: -1, Task: 0x0000000005177948, (Coordinator), Exchange Wait Type: e_waitPipeGetRow, Merging: 0
2011-05-19 14:00:15.610 spid23s       ResType:ExchangeId Stype:'AND' SPID:284 BatchID:0 ECID:0 TaskProxy:(0x00000002E188E510) Value:0x5177948 Cost:(0/10000)
2011-05-19 14:00:15.610 spid23s      NULL
2011-05-19 14:00:15.610 spid23s      Victim Resource Owner:
2011-05-19 14:00:15.610 spid23s       ResType:LockOwner Stype:'OR'Xdes:0x000000039F83AE90 Mode: U SPID:215 BatchID:0 ECID:0 TaskProxy:(0x00000002A9A8E538) Value:0xd45ccfc0 Cost:(0/0)
2011-05-19 14:00:15.610 spid34s      deadlock-list
2011-05-19 14:00:15.610 spid34s       deadlock victim=process4c51948
2011-05-19 14:00:15.610 spid34s        process-list
2011-05-19 14:00:15.610 spid34s         process id=process4c51948 taskpriority=0 logused=0 waitresource=PAGE: 28:1:17381 waittime=5023 ownerId=3636483745 transactionname=UPDATE lasttranstarted=2011-05-19T14:00:10.593 XDES=0x39f83ae90 lockMode=U schedulerid=5 kpid=10884 status=suspended spid=215 sbid=0 ecid=0 priority=0 trancount=2 lastbatchstarted=2011-05-19T14:00:02.070 lastbatchcompleted=2011-05-19T14:00:02.070 clientapp=.Net SqlClient Data Provider hostname=xxxhostpid=3544 loginname=test\xxxisolationlevel=read uncommitted (1) xactid=3636483745 currentdb=28 lockTimeout=4294967295 clientoption1=673185824 clientoption2=128056
2011-05-19 14:00:15.610 spid34s          executionStack
2011-05-19 14:00:15.610 spid34s           frame procname=mnAlert.dbo.up_BulkMailSchedule_Get_Items_To_Process line=18 stmtstart=1030 stmtend=2584 sqlhandle=0x03001c007488435bbfd1b600a69e00000100000000000000
2011-05-19 14:00:15.610 spid34s      UPDATE TOP (2048) dbo.BulkMailSchedule
2011-05-19 14:00:15.610 spid34s         SET
2011-05-19 14:00:15.610 spid34s             SelectID = @NewSelectID,
2011-05-19 14:00:15.610 spid34s             ProcessingStatusID = 2,
2011-05-19 14:00:15.610 spid34s             ProcessingStatusDate = GETDATE(),
2011-05-19 14:00:15.610 spid34s             ProcessingServer = @ProcessingServer,
2011-05-19 14:00:15.610 spid34s             LastAttemptDate = @CurrentDate,
2011-05-19 14:00:15.610 spid34s             NextAttemptDate = dbo.calcNextAttemptDate(@CurrentDate, Frequency, '02:00:00')
2011-05-19 14:00:15.610 spid34s         OUTPUT
2011-05-19 14:00:15.610 spid34s             inserted.MemberID,
2011-05-19 14:00:15.610 spid34s             inserted.GroupID AS CommunityID,
2011-05-19 14:00:15.610 spid34s             inserted.BulkMailTypeID,
2011-05-19 14:00:15.610 spid34s             inserted.Frequency,
2011-05-19 14:00:15.610 spid34s             inserted.LastSentDate,
2011-05-19 14:00:15.610 spid34s             inserted.LastAttemptDate,
2011-05-19 14:00:15.610 spid34s             inserted.NextAttemptDate,
2011-05-19 14:00:15.610 spid34s             inserted.SentCount,
2011-05-19 14:00:15.610 spid34s             inserted.FrequencyUpdateDate,
2011-05-19 14:00:15.610 spid34s             inserted.InsertDate,
2011-05-19 14:00:15.610 spid34s             inserted.SentMemberIDList
2011-05-19 14:00:15.610 spid34s         WHERE
2011-05-19 14:00:15.610 spid34s             SelectID is NULL AND 
2011-05-19 14:00:15.610 spid34s             NextAttemptDate <= GetDate() AND 
2011-05-19 14:00:15.610 spid34s             LastLogonDate > dateadd(dd,-@MaxDaysSinceLastLogin,GETDATE())
2011-05-19 14:00:15.610 spid34s         -- Return search prefs needed     
2011-05-19 14:00:15.610 spid34s          inputbuf
2011-05-19 14:00:15.610 spid34s      Proc [Database Id = 28 Object Id = 1531152500]    
2011-05-19 14:00:15.610 spid34s         process id=process5143b88 taskpriority=0 logused=0 waitresource=PAGE: 28:1:26081 waittime=3380 ownerId=3636479354 transactionname=UPDATE lasttranstarted=2011-05-19T14:00:03.183 XDES=0x2b0419970 lockMode=U schedulerid=11 kpid=2608 status=suspended spid=238 sbid=0 ecid=0 priority=0 trancount=2 lastbatchstarted=2011-05-19T14:00:03.183 lastbatchcompleted=2011-05-19T14:00:03.183 clientapp=.Net SqlClient Data Provider hostname=xxxhostpid=380 loginname=test\xxxisolationlevel=read uncommitted (1) xactid=3636479354 currentdb=28 lockTimeout=4294967295 clientoption1=673185824 clientoption2=128056
2011-05-19 14:00:15.610 spid34s          executionStack
2011-05-19 14:00:15.610 spid34s           frame procname=mnAlert.dbo.up_BulkMailSchedule_Get_Items_To_Process line=18 stmtstart=1030 stmtend=2584 sqlhandle=0x03001c007488435bbfd1b600a69e00000100000000000000

Answer 1

看起来您没有适当的索引。查看dbo.BulkMailSchedule表并查看可用的索引。你有NextAttempdate或LastLogonDate的索引以及这个表上的CI是什么？此类函数[dbo.calcNextAttemptDate]也可能无法很好地扩展。

你要解决这类问题的唯一方法就是花时间阅读更多关于死锁的内容。

参考http://blogs.msdn.com/b/bartd/archive/tags/sql+deadlocks/

中的文章

Answer 2

解决死锁的步骤：

识别死锁中涉及的代码（已完成）

确定根据需要重现死锁的方法

确定所涉及的每个代码集所需的隔离方法

删除更新中的所有计算值并替换为静态值（函数调用等）

注释掉所涉及代码的所有数据插入或更新

尝试重现死锁

如果死锁仍然存在，则涉及其他代码，请重新开始

在一组代码中启用插入或更新

尝试重现死锁

如果发生死锁，请调查其他带有锁定的spid

启用另一组代码中的一半插入

尝试重现死锁

如果发生死锁，请注释掉一半未注释的插入或更新

重复最后两步，直到找出死锁的原因

更新SQL Server中存储的proc死锁

2 个答案: