Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to determine what kind of locking do you have on SQL Server tables
- Thread starter request
- Start date
WilliamMathias
Programmer
Hi,
Your transaction isolation level determines your level of locking.
Default is Read Committed.
See this article for further details.
Will
Your transaction isolation level determines your level of locking.
Default is Read Committed.
See this article for further details.
Will
- Thread starter
- #3
WilliamMathias
Programmer
Hi,
The following is an extract that hopfully answers your question:
Another type of system table isn't really a table; it's a pseudo-table. Pseudo-tables take up no space and aren't stored permanently on disk. Instead, SQL Server builds them dynamically every time you query them. Storing these tables on disk usually doesn't make sense because their values represent volatile information within SQL Server that exists only while the server is running. For example, storing syslockinfo on disk would be meaningless because locks don't exist unless SQL Server is running. Also, lock information needs to be accessed so often and so quickly that storing it in a table would be too slow. SQL Server stores the information in internal memory structures and displays it as a table when you request it. You can use the following statement to select from syslockinfo as if it were a table:
SELECT * FROM master..syslockinfo
In addition, the stored procedure sp_lock retrieves information from syslockinfo Will
The following is an extract that hopfully answers your question:
Another type of system table isn't really a table; it's a pseudo-table. Pseudo-tables take up no space and aren't stored permanently on disk. Instead, SQL Server builds them dynamically every time you query them. Storing these tables on disk usually doesn't make sense because their values represent volatile information within SQL Server that exists only while the server is running. For example, storing syslockinfo on disk would be meaningless because locks don't exist unless SQL Server is running. Also, lock information needs to be accessed so often and so quickly that storing it in a table would be too slow. SQL Server stores the information in internal memory structures and displays it as a table when you request it. You can use the following statement to select from syslockinfo as if it were a table:
SELECT * FROM master..syslockinfo
In addition, the stored procedure sp_lock retrieves information from syslockinfo Will
- Status
Similar threads
- Locked
- Question
- Locked
- Question
