{"id":3195,"date":"2022-04-10T16:30:11","date_gmt":"2022-04-10T09:30:11","guid":{"rendered":"https:\/\/www.sqlservertutorial.net\/?page_id=3195"},"modified":"2022-04-10T16:58:04","modified_gmt":"2022-04-10T09:58:04","slug":"sql-server-blocking","status":"publish","type":"page","link":"https:\/\/www.sqlservertutorial.net\/sql-server-administration\/sql-server-blocking\/","title":{"rendered":"SQL Server Blocking"},"content":{"rendered":"\n

Summary<\/strong>: in this tutorial, you’ll learn about the SQL Server Blocking concept and fully understand it via an example.<\/p>\n\n\n\n

Introduction to the SQL Server blocking #<\/a><\/h2>\n\n\n\n

A block ( or blocking block) occurs when two sessions attempt to update the same data concurrently.<\/p>\n\n\n\n

The first session locks the data and the second session needs to wait for the first one to complete and release the lock. <\/p>\n\n\n\n

As the result, the second session is blocked from updating the data. Once the first session completes, the second session resumes operation. <\/p>\n\n\n\n

In general, blocking occurs when one session holds a lock on a resource and a second session attempts to acquire a conflicting lock type on the same resource.<\/p>\n\n\n\n

The following picture illustrates SQL Server blocking:<\/p>\n\n\n\n

\"SQL<\/figure>\n\n\n\n

Typically, the time in which the first session locks the data is very short. When it releases the lock, the second session can acquire its own lock on the resource and continue processing. <\/p>\n\n\n\n

Blocking is an unavoidable and by-design feature of SQL Server with lock-based concurrency. It is normal behavior and doesn’t impact the server performance.<\/p>\n\n\n\n

SQL Server blocking example #<\/a><\/h2>\n\n\n\n

We’ll create a new HR database with a table called People<\/code> for the demonstration:<\/p>\n\n\n

DROP<\/span> DATABASE<\/span> IF<\/span> EXISTS<\/span> HR;\nGO \n\nCREATE<\/span> DATABASE<\/span> HR;\nGO\n\nUSE<\/span> HR;\n\nCREATE<\/span> TABLE<\/span> People (\n  Id<\/span> int<\/span> IDENTITY<\/span> PRIMARY KEY<\/span>,\n  FirstName varchar<\/span>(50<\/span>) NOT<\/span> NULL<\/span>,\n  LastName varchar<\/span>(50<\/span>) NOT<\/span> NULL<\/span>\n);\n\n\nINSERT<\/span> INTO<\/span> People (FirstName, LastName)\nVALUES<\/span>  ('Jane'<\/span>, 'Doe'<\/span>);\n\n\nSELECT<\/span> * FROM<\/span> People;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
The People<\/code> table has one row with Id 1. <\/p>\n\n\n\n
First, begin a transaction and update the LastName<\/code> of the row with Id 1 to 'Smith'<\/code>:<\/p>\n\n\n
BEGIN<\/span> TRAN;\n\nUPDATE<\/span> People\nSET<\/span> LastName = 'Smith'<\/span>\nWHERE<\/span> Id<\/span> = 1<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Note that we did not commit or rollback the transaction in the first session.<\/p>\n\n\n\n
Second, create a new session. In the second session, update the LastName<\/code> of the row with id 1 to ‘Brown’:<\/p>\n\n\n
BEGIN<\/span> TRAN;\n\nUPDATE<\/span> People\nSET<\/span> LastName = 'Brown'<\/span>\nWHERE<\/span> Id<\/span> = 1<\/span>;\n\nCOMMIT<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Since the transaction in the first session is ongoing, the second session will wait for the first session to complete. <\/p>\n\n\n\n
If you use SQL Server Management Studio, you’ll see the following message:<\/p>\n\n\n
Executing query....<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
To list all the processes that are currently connected to the SQL Server, you use the sp_who2 stored procedure.<\/p>\n\n\n
sp_who2;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
The output shows that the system process ID (SPID) 55 is blocked by SPID 69. In this example, the first session is 69 while the second session is 55. Note that your SPID may be different from the ones in this example.<\/p>\n\n\n\n
\"SQL<\/figure>\n\n\n\n
Third, go back to the first transaction and commit it:<\/p>\n\n\n
COMMIT<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
As soon as the first session completes its transaction, the second session also completes.<\/p>\n\n\n\n
Summary #<\/a><\/h2>\n\n\n\n
  • Blocking occurs when two sessions attempt to update a resource at the same time. The second session is blocked because it has to wait for the second session to complete.<\/li>
  • Use the sp_who2<\/code> stored procedure to check which SPID  is blocked by another SPID.<\/li><\/ul>\n
    \n\t
    \n\t\t
    Was this tutorial helpful?<\/div>\n\t\t
    \n\t\t\t\n\t\t\t\t\n\t\t\t\t\t<\/path>\n\t\t\t\t<\/svg>\n\t\t\t\t Yes <\/span>\n\t\t\t<\/button>\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\t<\/path>\n\t\t\t\t<\/svg>\n\t\t\t\t No <\/span>\n\t\t\t<\/button>\n\t\t<\/div>\n\t<\/header>\n\n\t
    \n\t\t
    \n\t\t\t
    <\/div>\n\t\t\t\n\t\t\t