InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 06:59:26 GMT20http://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxTo 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.Wed, 28 May 2008 00:18:00 GMTAvishkar Meshramhttp://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxYou dont need to kill the process because SQL Server automatically kills the process that is creating that deadlock by using its internal deadlock manager.Tue, 27 May 2008 06:43:55 GMTalimcitphttp://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxif 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.Sat, 24 May 2008 14:35:38 GMTmobashahttp://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxIf 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?Sat, 24 May 2008 14:22:50 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxIn 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.aspxManu JaidkaFri, 23 May 2008 15:05:37 GMTMANU-J.http://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxThere 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.Fri, 23 May 2008 09:46:54 GMT Jack Corbetthttp://www.sqlservercentral.com/Forums/Topic505968-146-1.aspxIf 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 processingPlz guide me.Fri, 23 May 2008 09:32:46 GMTsandhyarao49