为什么锁监视器不能自动处理死锁
为什么sql-server锁监视器线程无法解决死锁？
我对此没有太多细节，但我的朋友抱怨 SQL Server（2005 和 2008）数据库上不时发生死锁。
据我所知，Sql Server 死锁检测机制可以很好地处理死锁场景，方法是选择其中一个进程作为受害者并终止/回滚它，以便另一个进程可以完成，这样就不会留下任何死锁需要解决。
是否存在 SQL Server 死锁处理可能失败或可能被关闭的情况？
提前致谢
Why would sql-server lock monitor thread would not resolve deadlocks?
I don't have much details about this, but my friends complain about deadlocks occuring from time to time on SQL Server (2005 & 2008) databases.
As I know, Sql Server deadlock detection mechanism handles deadlock scenarios pretty well by choosing one of the processing as the victim and terminating/rolling it back, so the other process can complete, so no deadlocks would be left there to resolve.
Are there any conditions where SQL Server deadlock handling might fail, or it might be turned off?
thanks in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
死锁处理只能导致一个连接被终止。
这是死锁情况的唯一解决方案，当两个进程相互阻塞时会发生死锁情况。所以两者都无法继续，必须中止
Deadlock handling can only result in one connection being killed.
This is the only resolution to a deadlock sitution, which happens when 2 process are blocking each other. So neither can proceed and one must be aborted