00:13:20.38 spid4s SPID: 91 ECID: 0 Statement Type: UPDATE Line #: 85 00:13:20.38 spid4s Input Buf: RPC Event: Proc It's just like session1 locks all records that will be in the same page and not yet committed? (we're using sql 2005 sp 4034, read_committed_with_snapshot isolation model) If I commit first Session2, then session1 does not take an U key lock. > Session1 is waiting on a U KEY lock on the row inserted by session2. Update testlock set statusid = 90 where groupid = 1 ![]() Insert into testlock(groupid, statusid) values (2,0) ![]() ![]() Insert into testlock(groupid, statusid) values (1,0) NOT NULL CONSTRAINT DEFAULT ((0)),ĬONSTRAINT PRIMARY KEY CLUSTERED I'm having a table with a clustered index (identity) and some other columns, where another column contains a grouping (so multiple PK are contained within one groupid).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |