SQL Server Deadlocks (SQL Server 2000)?

It depends on why they are getting the deadlocks at the moment. Without investigation of the cause it is impossible to say.

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.

I suppose we will get a nice graph in 2008. That probably won't appease the customer though - I just want the problem to go away! I think I'll advise it may sort the problem out - together with archiving some of the million records on this table.

– Colin Hale Jul 23 '10 at 11:46.

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.

I get what you're saying, but this is 1 customer out of 170+ customers getting deadlocks where other customers don't. – Colin Hale Jul 23 '10 at 10:39 1 Probably because of his custom SQL. Old rule that mostly applies n these scenarios: custom SQL = no support, but pay us for consulting.

– TomTom Jul 23 '10 at 10:42.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.