SQL Server 2000 - 调试死锁 [英] SQL Server 2000 - Debugging Deadlocks

问题描述

我正在寻找有关如何调试和追逐SQL Server 2000数据库中的死锁问题的建议。我已经建议我使用跟踪标志1024和3605，我已经找到给我以下内容：

I'm looking for suggestions on how to debug and chase down deadlock issues in an SQL Server 2000 database. I've had it recommended to me to use trace flags 1024 and 3605, which I have found give me the following:

1024 - 此跟踪标志返回锁的类型参与僵局和目前的命令受到影响。

1024 - this trace flag returns the type of locks participating in the deadlock and the current command affected.

3605 - 此跟踪标志将跟踪输出发送到错误日志。

3605 - this trace flag sends trace output to the error log.

具体的存储过程，表和索引仍然需要被发现，所以目标是使用这些跟踪标志。然后从那里我会更好地了解哪些索引需要调优，锁定调优查询的提示和潜在的sproc错误来修复。

The specific stored procedures, tables and indexes still need to be uncovered, so the goal is to use these trace flags to do so. And then from there I'll know better what indexes need tuning, locking hints for tuning queries, and potential sproc bugs to fix.

任何其他建议或快乐的结束战争故事

Any other suggestions or happy ending war stories on chasing down this all to common problem?

推荐答案

这是有关死锁故障排除的圣经： http://blogs.msdn.com/bartd/archive/2006/ 09/09 / Deadlock-Troubleshooting_2C00_-Part-1.aspx

Here is the bible on deadlock troubleshooting: http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx

这篇关于SQL Server 2000 - 调试死锁的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！