Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 locking behavior question
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Posting Yak Master

144 Posts

Posted - 12/15/2004 :  11:21:25  Show Profile  Reply with Quote

We are running a transaction1 in Read committed mode in which we are inserting into a table and selecting from 2nd table like:
Insert into tab1 select * from tabl2
Also in transaction2 we want to insert into table2 like
Bulk insert tab2…….
Strangely, trans1 is holding X lock on page of tab2 (so trans2 is waiting for this page to be released) so we have 3 questions/doubts:
1) Why SQL Server needs X lock on a page for select statement
2) 2nd problem is SQL Server is not holding IX lock on a table2 in trans1 so howcome SQL Server have X lock on a page without IX lock on table
3) Trans2 is able to get BU lock on a table but waiting for X lock on a page that is hold by trans1 (this is problem since trans1 should have IX lock on a table so that BU lock for trans2 should also not be granted)

Any opinion or suggestions will be appreciated for this locking behavior.


  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000