.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Articles >> DataBase >> Post New Resource Bookmark and Share   

 Subscribe to Articles

Understanding and handling SQL Server Transaction Deadlocks.

Posted By:Vishal Nayan       Posted Date: September 01, 2011    Points: 200    Category: DataBase    URL: http://www.dotnetspark.com  

Understanding and handling SQL Server Transaction Deadlocks.
 

Understanding and handling SQL Server Transaction Deadlocks.

 

Introduction: Deadlock occurs when two users have locks on separate objects and each user wants a lock on the other's object. When this happens, SQL Server ends the deadlock by automatically choosing one and aborting the process, allowing the other process to continue. The aborted transaction is rolled back and an error message is sent to the user of the aborted process. Generally, the transaction that requires the least amount of overhead to rollback is the transaction that is aborted.

Deadlock due to transaction: Let us take a scenario where a transaction X attempts to update table 1 and subsequently read/update data from table 2. At the same time there is another transaction Y which is trying to update table 2, and subsequently read /update data from table 1. In this scenario, transaction X holds lock that transaction Y needs to complete its tasks and vice versa. So in this scenario neither a transaction can complete until the other transaction release

Transaction deadlock situation:

Transaction X:

BEGIN TRAN

 

UPDATE EMPLOYEE SET EMPLOYEENAME='NAYAN VISHAL' WHERE EMPLOYEEID=111

WAITFOR DELAY '00:00:05'

UPDATE SALARY SET BASIC= 5000 WHERE EMPLOYEEID=111

 

COMMIT TRAN

Transaction Y:

BEGIN TRAN

 

UPDATE SALARY SET HRA=8500 WHERE EMPLOYEEID=111

WAITFOR DELAY '00:00:05'

UPDATE EMPLOYEE SET EMPLOYEENAME='BUMPY' WHERE EMPLOYEEID=111

 

COMMIT TRAN

Result:

(1 row(s) affected)

Msg 1205, Level 13, State 45, Line 5

Transaction (Process ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

 

Reason for above deadlock: What we did is we copied these two transactions in two different query window and run then simultaneously. Consequently what happen is that Transaction X locks and updates Employee table whereas transaction X locks and updates Salary table. After a delay of 20 ms, transaction X looks for the lock on Salary table which is already held by transaction Y and transaction Y looks for lock on Employee table which is held by transaction X. So both the transactions cannot proceed further, the deadlock occurs and the SQL server returns the error message 1205 for the aborted transaction.

How deadlock is resolved: User can choose which process should stop to allow other process to continue. SQL Server automatically chooses the process to terminate which is running completes the circular chain of locks. Sometime, it chooses the process which is running the  for shorter period then other process. But it is recommended that we should provide solution for handling deadlocks is to find the problem in our query code and then modify our processing to avoid deadlock situations. 

Let us rewrite our transaction query

Transaction X:

 

RETRY:

BEGIN TRAN

BEGIN TRY

      UPDATE EMPLOYEE SET EMPLOYEENAME='NAYAN VISHAL' WHERE EMPLOYEEID=111

      WAITFOR DELAY '00:00:10'

      UPDATE SALARY SET BASIC= 5000 WHERE EMPLOYEEID=111

      COMMIT TRAN

END TRY

BEGIN CATCH

      PRINT 'Rollback Transaction'

      ROLLBACK TRANSACTION

      IF ERROR_NUMBER() =1205 -- DEADLOCK NUMBER

      BEGIN

            WAITFOR DELAY '00:00:00.05'

            GOTO RETRY

      END

END CATCH

 

Transaction Y:

 

RETRY:

BEGIN TRAN

BEGIN TRY

      UPDATE SALARY SET HRA=8500 WHERE EMPLOYEEID=111

      WAITFOR DELAY '00:00:10'

      UPDATE EMPLOYEE SET EMPLOYEENAME='BUMPY' WHERE EMPLOYEEID=111

      COMMIT TRAN

END TRY

BEGIN CATCH

      PRINT 'Rollback Transaction'

      ROLLBACK TRANSACTION

      IF ERROR_NUMBER()=1205

      BEGIN

            WAITFOR DELAY '00:00:00.05'

            GOTO RETRY

      END

END CATCH

 

Explanation:

TRY /CATCH can be used for error handing within the transaction. If there is code failure with TRY block , the control comes in CATCH statement which ultimately rollbacks the transaction. Here we are checking if the error code is 1205 which corresponds to transaction, then transaction waits for 5 ms. This delay is necessary for other transaction to complete within delay duration and release the lock from the table. So after the delay, the transaction starts executing from the beginning using RETRY statement.

Result: If we run these two Trans statement at the same time, we will get below result.

 

(1 row(s) affected)

Rollback Transaction

 

(1 row(s) affected)

 

(1 row(s) affected)

 

Tips to avoid deadlocks:

1. Minimize the size of transaction and transaction times.

2. Always access server objects in the same order each time in application.

3. Avoid cursors, while loops or process which requires user input while it is running.

4. Reduce lock time in application.

5. Use query hints to prevent locking if possible (NoLock, RowLock)

6. Select deadlock victim by using SET DEADLOCK_PRIORITY.

 

How to keep track of DEADLOCK in SQL Server: By Default SQL Server doesn't keep track of DEAD LOCKs, we as a DBA need to request SQL Server to keep track of DEAD LOCKs in SQL Server Error Log. 

Sql server by default doesn't keep track of deadlock, we have to manually configure sql server to track deadlock in sql server error log. So when lets us see below what information we need to provide sql server for this.

 

a) What to Capture?

b) Where to capture?

c) Define Scope, from where you want to capture?

DBCC TRACEON (3605,1204,1222,-1)

 

/*

-- where

-- What to Capture?

--------------------

  -- (1204) = Capture Deadlock Events.

  -- (1222) = Capture Deadlock Events with detailed Information (works only with SQL 2005 and higher version)

-- Where to capture ?

-------------------

   -- (3605) = Capture the selected Events in the SQL Server error log.

-- What is the Scope of Capture

--------------------------------

    -- (-1) = Switches on the specified trace flags globally, that means do it globally, for all users/sessions

*/

This won't work if an instance of sql server is not working, so moment we restart sql server, we need to do this again. To configure this permanently follow the instruction below

a) Create a SQL Agent job and put this code into and schedule that job to when the Agent starts  

b) You need to enable this trace flags at SQL Server startup parameter, by specifying  -T1222; -T3605; in the startup parameter.

1) SQL Server Configuration Manager à SQL Server Services -> right-click SQL Server () -> Properties -> Advanced TAB -> Startup Parameters box -> type the parameters separated by semicolons (;).

 

Hope you enjoyed reading

Cheers!


 Subscribe to Articles

     

Further Readings:

Responses

No response found. Be the first to respond this post

Post Comment

You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend