Posted by Erland Sommarskog on 02/05/06 00:50

Joe Weinstein (joeNOSPAM@bea.com) writes:
> Ok. Thanks. However, by default, with SQL2005, why is this a deadlock?

I didn't touch that part, as it was already explained in other post, but
in case you missed it.

First both processes inserts a row into the table, and maintain a lock
as the INSERTs are not committed. Next, they try to read the entire table.
But do that, session 1 needs to access the row inserted by session 2
and vice versa.




--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]