How to resolve a deadlock

Posted on 2007-11-29
Last Modified: 2012-08-14
I have been experiencing deadlock errors in my sql server 2000 database.  I have run DBCC TRACEON(1204) to identify whats causing the problem and the results are shown in the code snippet below.  I am now trying to identify what the problem is.  It seems that under Node 2, the stored procedure SnapPriceRateBuffers has requested an exclusive lock on TableA.  Under Node 1, stored procedure remote_GetDataAll is performing a SELECT INTO a temporary table (lets say #TableB).  This SELECT INTO statement is sourcing data from TableA in the FROM clause but I don't understand why this situation would cause a deadlock.  Is it possible to explain what is going on from the results of the error log?

2007-11-29 11:13:09.16 spid2     Wait-for graph
2007-11-29 11:13:09.16 spid2     
2007-11-29 11:13:09.16 spid2     Node:1
2007-11-29 11:13:09.16 spid2     RID: 7:1:25386:11              CleanCnt:1 Mode: U Flags: 0x2
2007-11-29 11:13:09.16 spid2      Grant List 0::
2007-11-29 11:13:09.16 spid2      Grant List 1::
2007-11-29 11:13:09.16 spid2        Owner:0x5164a880 Mode: S        Flg:0x0 Ref:1 Life:00000000 SPID:53 ECID:0
2007-11-29 11:13:09.16 spid2        SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 34
2007-11-29 11:13:09.18 spid2        Input Buf: RPC Event: remote_GetDataAll;1
2007-11-29 11:13:09.18 spid2      Requested By: 
2007-11-29 11:13:09.18 spid2        ResType:LockOwner Stype:'OR' Mode: X SPID:52 ECID:0 Ec:(0x76AFD578) Value:0x467028c0 Cost:(0/17A58)
2007-11-29 11:13:09.18 spid2     
2007-11-29 11:13:09.18 spid2     Node:2
2007-11-29 11:13:09.18 spid2     RID: 7:1:1830:27               CleanCnt:1 Mode: X Flags: 0x2
2007-11-29 11:13:09.18 spid2      Grant List 0::
2007-11-29 11:13:09.18 spid2        Owner:0x1ade6200 Mode: X        Flg:0x0 Ref:0 Life:02000000 SPID:52 ECID:0
2007-11-29 11:13:09.18 spid2        SPID: 52 ECID: 0 Statement Type: UPDATE Line #: 63
2007-11-29 11:13:09.18 spid2        Input Buf: RPC Event: SnapPriceRateBuffers;1
2007-11-29 11:13:09.18 spid2      Requested By: 
2007-11-29 11:13:09.18 spid2        ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x6A09D578) Value:0x462bdce0 Cost:(0/0)
2007-11-29 11:13:09.18 spid2     Victim Resource Owner:
2007-11-29 11:13:09.18 spid2      ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x6A09D578) Value:0x462bdce0 Cost:(0/0)

Open in new window

Question by:nicksbell
  • 3
  • 3
LVL 48

Expert Comment

by:Vitor Montalvão
ID: 20375991
Deadlocks happens when a query is locking a resource and tries to work with other resource that is already locked by another process and that process at same time tries to access the resource locked by 1st process. (I hope isn't confusing) :)

This is a programming issue and DBA can't do nothing about it. SQL Server will choose one of the process as victim and you kill it, freeing resources to the process that's kept alive.

It needs to change queries to use locking hints or create indexes to speed up queries.

Good luck

Author Comment

ID: 20376123
What I am trying to understand is why the following 2 sql statements might cause a deadlock.  This is a simplified example of what is happening in my actual situation.

Statement 1

    Column1 = 'xxx'

Statement 2


These are the 2 processes that are causing the deadlock and I am trying to understand how this could fit into the the scenario you describe for deadlocks to occur.
LVL 48

Expert Comment

by:Vitor Montalvão
ID: 20376155
Well, UPDATE don't have a WHERE clause, so SQL Server will lock all table.
SELECT doesn't have a WHERE clause either, so to SQL Server guarantee that all records that will being copied to TempTable will be the same that are in TableA, will need to lock all table as well.

But that scenario should only cause a blocking lock and not a deadlock.
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.


Author Comment

ID: 20376245
The situation is actually a lot more complicated than I described above as I was trying to simplify things.  There are more tables (e.g. TableC and TableD) involved through joins in the SELECT statement 2 and TableA has triggers that update TableC and TableD.  Is it possible to identify exactly which table is the locked resource from the error log?
LVL 48

Accepted Solution

Vitor Montalvão earned 500 total points
ID: 20376304
Ok. If there's more tables than it's like that you are having really deadlocks.
You should check if UPDATE and SELECT are using the best indexes. Usually deadlock happens when processing a big amount of data. Having the correct indexes, will be faster enough to process requests avoiding deadlocks.
If indexes are ok, then you can use a workaround, that's locking hints. The problem is that you never know if you'll work with dirty data.

Use SELECT columns FROM TableA with (nolock), TableB with (nolock), ...

This avoid locks on table, but will bring all data that wasn't be commited and can be rolled back.

Good luck

Author Closing Comment

ID: 31411748
ok, I will try that.  It might take a while before I can be sure it worked as the deadlocks don't happen all the time but you have been very helpful so you can have the points.

Thanks for your help.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction In my previous article ( I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question