We have an application running well for a long time on SQL2000 SP3a.
Few days ago we have installed SP4 and immediately after this some users
started to get errors:
"Transaction (Process ID XXX) was deadlocked on lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction."
When I look in the process info it seems that this process is blocked by itself, i.e. the blocking process and the blocked
one have the same id.
Moreover, there is no explicit transactions in the whole application. Each statement is executed separately. Transaction
isolation level has been set to read_uncommitted.
After some investigation we desided to roll back to SP3a and it seems to solve the problem.
Any other solution?