July 28, 2003 at 5:14 pm
Looks like every connection places a shared database lock on the database to which they connect. Now you would think a shared database lock might place the database into a read-only mode, meaning no updates/inserts/deletes could occur while the database shared lock is in place. But this does not seem the case.
Does anyone know where I can find out some specific information about a database shared lock. I'd like to know more about what kind of commands would be blocked due to a database shared lock.
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Gregory A. Larsen, MVP
July 28, 2003 at 5:42 pm
Database locks are not part of the "by-the-textbook" lock hierarchy that is used by tables (object - page - row). A database lock just means someone is connected to that database. It doesn't affect any of the DATA in that database.
When you try to do something like drop or detach a database, you can't do it if there are any users. SQL Server determines whether there are any users by checking for database locks.
quote:
Looks like every connection places a shared database lock on the database to which they connect. Now you would think a shared database lock might place the database into a read-only mode, meaning no updates/inserts/deletes could occur while the database shared lock is in place. But this does not seem the case.Does anyone know where I can find out some specific information about a database shared lock. I'd like to know more about what kind of commands would be blocked due to a database shared lock.
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply