Skip to main content

LOCK in SQL Server

In SQL Server 2000 (Enterprise Manager)

1. Expand server – management-current Activity-expand
Locks/processid and you will be able to see all the locks related information.

2. Expand server – management-current Activity-expand Locks/object you can see locks by object information.

In SQL Server 2005 (SSMS, object Explorer)

Expand-server-management-double click Activity Monitor.

On left side you have three options to choose from, select those options and you can see all the locks related information.

Run this stored procedure in the database.

1. sp_lock

To know the running process in the sql server, run this query,

2. select * from sysprocesses (in sql server 2000)
3. select * from sys.sysprocesses (in sql server 2005)

4. sp_who
5. sp_who2 will also give you some good information.

To work around the locks, you can run profiler to check which query is creating a lock and if that is necessary.

Types of locks on object level, (general idea)

Database: Database.
Extent: Contiguous group of eight data pages or index pages.
Key: Row lock within an index.
Page: 8-kilobyte (KB) data page or index page.
RID: Row ID, Used to lock a single row within a table.
Table: Entire table, including all data and indexes.

Types of locks:
Shared (S) – more than one Query can access the object.
Exclusive lock (X) – only one Query can access the object.
Update lock (U)
Intent share (IS)
Intent Exclusive (IX)

Just to give you a brief idea about locks, we have something called as transaction levels in sql server databases.



Level 0 is the lowest level isolation level, if your database is set in this isolation level, no query will lock any resources, under this level, and there will be no locks on the database, not even shared locks.


This data will also read uncommitted data. Data which you have not committed, you can still read that data.

Level1 is the default isolation level of the database.
Under this category you will not be able to read uncommitted data; this is also called as dirty data. Under this we will have shared locks.

As the level increases the locks also increases. The highest is the serializable.

To make you understand in detail, let’s see an example of what is committed data and what is uncommitted data.

use pubs
create table example1 ( eid int, ename varchar(10))

begin tran T1
insert into example1 values ( 1, ‘example’)

select * from example1 this is uncommitted data.

The above is uncommitted transaction, because you started the transaction with a begin, you have to commit the transaction, until then the transaction will not be uncommitted.

To commit the same transaction

commit tran T1

select * from example1 — this is committed data.

To check the current isolation level of your database, run this command,

Dbcc useroptions — check for isolation level.

If you don’t want your query to put locks on objects you might want to use something like this,

select * from example1_1 with (nolock)

This will not keep any lock, not even a shared lock on the table. This is the most effective way to avoid locks in SQL.

This is in-depth concept. Hope this will help someone.

Microsoft SQL Server 2005 UnleashedExpert SQL Server 2005 DevelopmentMicrosoft SQL Server 2005 For DummiesMaster Lock 178D Set-Your-Own Combination Padlock, Die-Cast, Black


Popular posts from this blog

Call User-defined Function on Linked Server :SQL Server

If you try to invoke a user-defined function (UDF) through a linked server in SQL Server by using a "four-part naming" convention (server.database.dbo.Function), you may receive error message.  The reason is User-defined function calls inside a four-part linked server query are not supported in SQL Server. Thats why error message indicates that the syntax of a Transact-SQL statement is incorrect.  To work around this problem, use the Openquery function instead of the four-part naming convention. For example, instead of the following query Select * from Linked_Server.database.dbo.Function(10) run a query with the Openquery function: Select * from Openquery(Linked_Server,'select database.dbo.Function(10)') If the user-defined function takes variable or scalar parameters, you can use the sp_executesql stored procedure to avoid this behavior.  For example: exec Linked_Server.database.dbo.sp_executesql N'SELECT database.dbo.Function(@input)',N'@input

Pass multiple complex objects to Web API action

Working with ASP.NET Web API, the most unexpected thing is the limited support of POST data values to simple ApiController methods. When a parameter has [FromBody], Web API uses the Content-Type header to select a formatter. At most one parameter is allowed to read from the message body. The reason for this rule is that the request body might be stored in a non-buffered stream that can only be read once. A simple principle, you can send any content in HTTP request, it only need to be serializable into a string. So, it could be multiple JSON object. In this example, the content type is "application/json" and the request body is a raw JSON string (not a JSON object). Here I found a workaround to pass multiple complex objects (using the above principle) from jquery to a WEB API using JObject , and then cast back to your required specific object type in api controller. This objects provides a concrete type specifically designed for working with JSON. var customer = { &quo

Installing the FrontPage Server Extensions on IIS 7.0

As most people that have installed IIS 7.0 on Windows Vista and Windows Server© 2008 have realized, there are no options to install the FrontPage Server Extensions, leaving only two ways to edit your Web site if it is hosted on a Windows Vista or Windows Server 2008 computer: Edit the Web site locally by using the file system. Use FTP to upload your files to a remote Windows Vista or Windows Server 2008 computer. Microsoft realizes that the FrontPage Server Extensions are essential to many Web hosting companies and developers, and has worked with Ready-to-Run Software to release a version of the FrontPage 2002 Server Extensions (FPSE 2002) for Windows Vista and Windows Server 2008. This version of FPSE 2002 is available for x86 (32-bit) and x64 (64-bit) Windows Vista and Windows Server 2008 as a separate download for IIS 7.0, and you can download this version by clicking the following URL: FrontPage 2002 Server Extensions for IIS 7.0 Notes: The FrontPage 2002 Server Extensions (