I'm seeing an interesting deadlock problem with SQL Server 2005 (2000 mode) where incomptible locks are being honoured (U & X). This was already granted before the deadlock & the each of the processes try to get a 'U' lock again and results in deadlock.
Deadlock graph is shown below. The table in question (PLTransactionSeq) is used for Sequencing & only has 1 record. It has a clustered index on the sequence field.
Did I read the deadlock graph incorrectly ?
View Complete Post