Posted by Erland Sommarskog on 02/04/06 23:52

Joe Weinstein (joeNOSPAM@bea.com) writes:
>> Two sessions:
>>
>> Session 1:
>> BEGIN TRAN
>> insert into joe (c1,c2) values (1,2)
>>
>>
>> Session 2:
>> BEGIN TRAN
>> insert into joe (c1,c2) values (3,4)
>>
>> Session 1:
>> select * from joe
>>
>> Session 2:
>> select * from joe
>>
>> One of the sessions gets a deadlock victim message.
>> thanks,
>> Joe
>
> PS: This doesn't occur with Sybase, which is fairly closely
> related...

Or was. I don't know what Sybase is doing these days. But neither would
you get a deadlock on SQL 2005 if you run with snapshot isolation.

And when I think of it, neither would this deadlock on SQL 6.5, as
Session 2 would block already on the INSERT, as it would be on a locked
page...


--
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

• Next in forum: SQL Server DB installation
• Prev in forum: Re: Views vs Stored Procedures, whats the difference?
• Thread view: Re: can you tell me why this causes a deadlock?

[Reply to this message]