SQL Server 死锁 (SQL Server 2000)
我有一位客户每天遇到 5 次以上的僵局。 170 多个其他客户根本没有遇到任何僵局。我已经实现了死锁跟踪，并且可以看到发生的选择/更新/插入死锁。我实现了 with (rowlock) 提示，这解决了最初的死锁。然而，事态进一步陷入僵局。
我发现客户正在运行自定义 SQL，这导致了一些问题，但不是全部。
我的问题确实是，有谁知道将客户从 sql server 2000 升级到 sql server 2008 是否可能解决该问题？
谢谢，
上校。
I have one customer experiencing 5+ deadlocks per day. 170+ other customers don't get any deadlocks at all. I've implemented deadlock tracing and can see the select/update/insert deadlocks occurring. I implemented a with (rowlock) hint and this sorted the initial deadlock out. However, the thing still deadlocks further on down the line.
I've discovered the customer is running custom SQL which has been causing some of the problems, but not all of them.
My question really is does anyone know whether upgrading the customer from sql server 2000 to sql server 2008 will likely fix the issue?
Thanks,
Col.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不认为使用 sql 2000 或 2008 之间会有任何差异。
实际上，只要推理造成僵局的原因就可以解决任何僵局
i don't think that there will be any differences between using sql 2000 or 2008.
Actually you can solve any deadlock just reasoning on the causes which created them
这取决于他们目前陷入僵局的原因。如果不调查原因，就无法确定。
与 SQL2000+ 相比，SQL 2005/2008 在这方面确实具有几个优点，即引入了快照隔离，可以消除一些死锁可能性，并提供更好的监视选项来深入了解死锁发生的原因。
It depends on why they are getting the deadlocks at the moment. Without investigation of the cause it is impossible to say.
A couple of advantages that SQL 2005/2008 do have in this area over SQL2000+ is the introduction of snapshot isolation that can remove some deadlock possibilities and better monitoring options to get to the bottom of why a deadlock is occurring.