>There's probably no problems at all. Deadlocks are a natural event in the life of a database. I wouldn't spend a lot of time trying to track down the players involved. You may never be able to do it.
>
>There are some MSDN articles that are worth looking at. Try starting here:
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servdatabse_5xrn.asp
>
>This link discusses a Trace flag that captures some debuging information about the threads involved in the deadlock and the resources that are locked.

Well certainly look into this. We have a mixture of SQL7 and SQL2K. This article metions only SQL2K. Is this an available option for SQL7?

>In the meantime, it has always been my opinion that an application should not error out due to a deadlock. Catch the error and resubmit the query. The other connections will probably have completed their work and released their locks.

We'll certainly look into doing just that. Right now, all we do is log the error and quit.

Thanks!