Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

deadlock Expand / Collapse
Author
Message
Posted Friday, May 23, 2008 9:32 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, February 18, 2013 9:50 PM
Points: 119, Visits: 650

If we have a Dead lock situation,we can check in the error log and find out which spids are involved in the process.After that the next step is to kill one of the process by using KILL (spid)

In this situation i have a small doubt can we able to directly issue a kill command.Is this approach correct one or any other solution is there.
And i want to know can we have to consider anything before issuing a
kill command.
Is this is the only solution or is there any approach.
And i have one more doubt , if we kill a process then what about the data that the transaction is processing

Plz guide me.
Post #505968
Posted Friday, May 23, 2008 9:46 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:24 AM
Points: 10,907, Visits: 12,540
There are a couple of things I would do before killing a process.

1. Run sp_lock [spid] for each spid to see what is object(s) are causing the deadlock and the types of locks. You will see a wait for the blocked spid.
2. Run DBCC InputBuffer([spid]) for each spid involved to find the statements that are causing the deadlock.

Once you find this you can then determine if indexing may help (possibly reduce the type of lock from table to page/row), refactor the code in the offending statements to access tables in the same order, and determine there are long-running transactions that can be broken down in to smaller transactions.




Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #505984
Posted Friday, May 23, 2008 3:05 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, February 27, 2014 11:17 AM
Points: 1,688, Visits: 8,756
In case you have recurring deadlock issues then go thru the link mentioned below and you really dont knwo how to troubleshoot them:

http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx

Manu Jaidka
Post #506148
Posted Saturday, May 24, 2008 2:22 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:59 AM
Points: 41,508, Visits: 34,425
If you have a true deadlock, then you won't need to kill processes. SQL has a deadlock detector that will notice a deadlock condition, pick one of the participants and kill it automatically.

Do you have true deadlocks (if so, the users will be getting occasional errors about processes been picked as the deadlock victim and rolled back) or do you just have long-term blocking?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #506267
Posted Saturday, May 24, 2008 2:35 PM


Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Sunday, January 29, 2012 1:45 AM
Points: 710, Visits: 1,284
if u killed a process its statment will be rolled back, so u dont have to wory that much.
but if the code have "begin transaction and commit transaction" if u killed the session after the commit then the roll back wont effect this batch.


..>>..

MobashA
Post #506272
Posted Tuesday, May 27, 2008 6:43 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, January 14, 2011 7:53 AM
Points: 78, Visits: 344
You dont need to kill the process because SQL Server automatically kills the process that is creating that deadlock by using its internal deadlock manager.

Basit Ali Farooq
MCITP Database Administrator
Microsoft Certified Professional Developer (Web Applications)
Microsoft Certified Database Administrator
Microsoft Certified Systems Engineer
Microsoft Certified Systems Administrator
CIW Security Analyst
Cisco Certified Network Associate
Post #506882
Posted Wednesday, May 28, 2008 12:18 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, October 02, 2013 2:22 AM
Points: 42, Visits: 314
To avoid deadlock, you must have through knowledge of your application.
1. Identify the deadlocking processes and the object sparticipating in deadlock.
2. Use program monitoring table, say Program_session having columns program_id and running_date and modify your SPs/or queries such that, it will first check entry in Program_session and verify if running_date is NULL.
3. If running_date is NULL, then SP can continue with setting running_date to getdate(). And after executing set running_date to NULL.
4. Else use wait() command to follow steps 3.
Post #507446
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse