Re: Data/index locking in SQL server
From: Andrew J. Kelly (sqlmvpnoooospam_at_shadhawk.com)
Date: 04/13/04
- Next message: Andrew J. Kelly: "Re: nvarchar vs varchar"
- Previous message: ajmiester: "Updating data based on timestamp"
- In reply to: Alex Drobyshev: "Re: Data/index locking in SQL server"
- Next in thread: Alexandre Drobychev: "Re: Data/index locking in SQL server"
- Reply: Alexandre Drobychev: "Re: Data/index locking in SQL server"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Apr 2004 21:03:43 -0500
Can you post the actual DDL including the indexes for that table? Is that
index on the key column clustered or non and if non is there a clustered at
all?
-- Andrew J. Kelly SQL MVP "Alex Drobyshev" <ad31415@yahoo.com> wrote in message news:52a3e1ca.0404091252.42392b7e@posting.google.com... > By "lock on the table" I actually meant a lock on a specific row in the > table, not a lock on the whole table. Similarly, "lock on the index" > means a lock on a specific key. > > Having said that, here are lock acquisition sequences I observed: > > SELECT: > - S (Key) > - S (Row) > > UPDATE: > - X (Row) > - X (Key) > > (I have omitted "U" locks, for they don't really change the behaviour > here). > > When SELECT and UPDATE both operate on the same row (and key), a > dedalock occurs. :-(
- Next message: Andrew J. Kelly: "Re: nvarchar vs varchar"
- Previous message: ajmiester: "Updating data based on timestamp"
- In reply to: Alex Drobyshev: "Re: Data/index locking in SQL server"
- Next in thread: Alexandre Drobychev: "Re: Data/index locking in SQL server"
- Reply: Alexandre Drobychev: "Re: Data/index locking in SQL server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|