gpt4 book ai didi

sql - 如何在单个进程中模拟SQL Server死锁?

转载 作者:行者123 更新时间:2023-12-01 21:16:24 28 4
gpt4 key购买 nike

我们的客户端代码检测死锁,等待一段时间,然后重试请求最多 5 次。重试逻辑根据错误号1205检测死锁。

我的目标是测试各种存储过程内部的死锁重试逻辑和死锁处理。我可以使用两个不同的连接来创建死锁。但是,我想在单个存储过程本身内部模拟死锁。

死锁会引发以下错误消息:

Msg 1205, Level 13, State 51, Line 1
Transaction (Process ID 66) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

我看到此错误消息位于sys.messages中:

select * from sys.messages where message_id = 1205 and language_id = 1033

message_id language_id severity is_event_logged text
1205 1033 13 0 Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

我无法使用 RAISERROR 引发此错误:

raiserror(1205, 13, 51)

Msg 2732, Level 16, State 1, Line 1
Error number 1205 is invalid. The number must be from 13000 through 2147483647 and it cannot be 50000.

我们的死锁重试逻辑检查错误号是否为 1205。死锁需要具有与正常死锁相同的消息 ID、级别和状态。

有没有一种方法可以模拟死锁(使用 RAISERROR 或任何其他方式)并仅用一个进程即可获取相同的消息编号?

我们的数据库使用 SQL 2005 兼容性,但我们的服务器从 2005 到 2008 R2 不等。

最佳答案

正如许多人指出的那样,答案是否定的,单个进程无法可靠地自行死锁。我想出了以下解决方案来模拟开发或测试系统上的死锁。

在 SQL Server Management Studio 窗口中运行以下脚本。 (仅在 2008 R2 上测试。)您可以根据需要让它运行。

在要模拟死锁的位置,插入对 sp_simulatedeadlock 的调用。运行您的进程,应该会发生死锁。

完成测试后,停止 SSMS 查询并运行底部的清理代码。

/*
This script helps simulate deadlocks. Run the entire script in a SQL query window. It will continue running until stopped.
In the target script, insert a call to sp_simulatedeadlock where you want the deadlock to occur.
This stored procedure, also created below, causes the deadlock.
When you are done, stop the execution of this window and run the code in the cleanup section at the bottom.
*/
set nocount on

if object_id('DeadlockTest') is not null
drop table DeadlockTest

create table DeadlockTest
(
Deadlock_Key int primary key clustered,
Deadlock_Count int
)
go

if exists (select * from sysobjects where id = object_id(N'sp_simulatedeadlock')
AND objectproperty(id, N'IsProcedure') = 1)
drop procedure sp_simulatedeadlock
GO

create procedure sp_simulatedeadlock
(
@MaxDeadlocks int = -1 -- specify the number of deadlocks you want; -1 = constant deadlocking
)
as begin

set nocount on

if object_id('DeadlockTest') is null
return

-- Volunteer to be a deadlock victim.
set deadlock_priority low

declare @DeadlockCount int

select @DeadlockCount = Deadlock_Count -- this starts at 0
from DeadlockTest
where Deadlock_Key = 2

-- Trace the start of each deadlock event.
-- To listen to the trace event, setup a SQL Server Profiler trace with event class "UserConfigurable:0".
-- Note that the user running this proc must have ALTER TRACE permission.
-- Also note that there are only 128 characters allowed in the trace text.
declare @trace nvarchar(128)

if @MaxDeadlocks > 0 AND @DeadlockCount > @MaxDeadlocks
begin

set @trace = N'Deadlock Test @MaxDeadlocks: ' + cast(@MaxDeadlocks as nvarchar) + N' @DeadlockCount: ' + cast(@DeadlockCount as nvarchar) + N' Resetting deadlock count. Will not cause deadlock.'
exec sp_trace_generateevent
@eventid = 82, -- 82 = UserConfigurable:0 through 91 = UserConfigurable:9
@userinfo = @trace

-- Reset the number of deadlocks.
-- Hopefully if there is an outer transaction, it will complete and persist this change.
update DeadlockTest
set Deadlock_Count = 0
where Deadlock_Key = 2
return
end

set @trace = N'Deadlock Test @MaxDeadlocks: ' + cast(@MaxDeadlocks as nvarchar) + N' @DeadlockCount: ' + cast(@DeadlockCount as nvarchar) + N' Simulating deadlock.'
exec sp_trace_generateevent
@eventid = 82, -- 82 = UserConfigurable:0 through 91 = UserConfigurable:9
@userinfo = @trace

declare @StartedTransaction bit
set @StartedTransaction = 0
if @@trancount = 0
begin
set @StartedTransaction = 1
begin transaction
end

-- lock 2nd record
update DeadlockTest
set Deadlock_Count = Deadlock_Count
from DeadlockTest
where Deadlock_Key = 2

-- lock 1st record to cause deadlock
update DeadlockTest
set Deadlock_Count = Deadlock_Count
from DeadlockTest
where Deadlock_Key = 1

if @StartedTransaction = 1
rollback
end
go

insert into DeadlockTest(Deadlock_Key, Deadlock_Count)
select 1, 0
union select 2, 0

-- Force other processes to be the deadlock victim.
set deadlock_priority high

begin transaction

while 1 = 1
begin

begin try

begin transaction

-- lock 1st record
update DeadlockTest
set Deadlock_Count = Deadlock_Count
from DeadlockTest
where Deadlock_Key = 1

waitfor delay '00:00:10'

-- lock 2nd record (which will be locked when the target proc calls sp_simulatedeadlock)
update DeadlockTest
set Deadlock_Count = Deadlock_Count
from DeadlockTest
where Deadlock_Key = 2

rollback

end try
begin catch
print 'Error ' + convert(varchar(20), ERROR_NUMBER()) + ': ' + ERROR_MESSAGE()
goto cleanup
end catch

end

cleanup:

if @@trancount > 0
rollback

drop procedure sp_simulatedeadlock
drop table DeadlockTest

关于sql - 如何在单个进程中模拟SQL Server死锁?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/11569964/

28 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com