CODEWITHSUNDEEP
sql-server-2008
user384080
user384080

Reputation: 4692

ROWLOCK in sql server

I have a table to update with no indexing in the where clause so I use ROWLOCK in the update script, hoping to get row lock instead of table lock but no luck.. so what is the function of the ROWLOCK then? I was using it in the select statement but still locking the entire table... so annoying!

Upvotes: 4

Views: 8144

Answers (1)

Oleg Dok
Oleg Dok

Reputation: 21766

If you selecting too many rows - Sql Server will escalate lock to table level. Instead you may hit the cap of possible locks count or memory

OR

You use SNAPSHOT isolation level - then you may only apply ROWLOCK hint with HOLDLOCK or UPDLOCK hints simultaneously

Update:

You may frame your statement with

DBCC TRACEON(-1,3604,1200) WITH NO_INFOMSGS;

Here is your statement

DBCC TRACEOFF(-1,3604,1200) WITH NO_INFOMSGS;

and see - which locks are taken, held and released during the run

UPDATED:

DBCC TRACEON (-1, 3604, 1200)

BEGIN TRAN

UPDATE [Order]

with (ROWLOCK)

SET ProductId = 3

WHERE CustomerId = 1

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Process 54 acquiring IX lock on OBJECT: 16:229575856:0 (class bit2000000 ref1) result: OK

Process 54 acquiring IU lock on PAGE: 16:1:196 (class bit0 ref1) result: OK

Process 54 acquiring U lock on RID: 16:1:196:0 (class bit0 ref1) result: OK

Process 54 acquiring IX lock on PAGE: 16:1:196 (class bit2000000 ref0) result: OK

Process 54 acquiring X lock on RID: 16:1:196:0 (class bit2000000 ref0) result: OK

Process 54 releasing lock reference on RID: 16:1:196:0

Process 54 acquiring U lock on RID: 16:1:196:1 (class bit0 ref1) result: OK

Process 54 releasing lock on RID: 16:1:196:1

Process 54 releasing lock reference on PAGE: 16:1:196

(1 row(s) affected)

Upvotes: 4

Related Questions