We have experienced deadlocks a couple of times with one of our third party applications which used sql 2000.
I've checked with the vendor and I've been told that the applications handles error 1222 by adding an entry to the applications log and dropping the transaction in which the error occurred.
I've also check the sql settings regarding lock time-outs and the timeout is set to -1.
is it possible to permanently set the lock time out to a different value? it defaults back to -1 when I logoff ?
What is a good time_out value, does it have to correspond with any setting on the application?
I'm I understanding this correctly that the deadlock is a result of lock which never timed out and by having the lock time_out set the locks should not deteriorate into a deadlock?