SQL Server Performance

What are ALL the reasons for why a deadlock is killed/cleared?

Discussion in 'SQL Server 2005 General DBA Questions' started by Trev256, Mar 26, 2009.

  1. Trev256 New Member

    Hi - Can someone please list what are ALL the reasons for why a deadlock is killed/cleared? I can list these as a starter - please add all others?
    1) You can manually kill the process.
    2) SQL Server detects the deadlock and kills and rollsback the least expensive (in terms of work done).
    3) Deadlock priority is set and the process with the lowest set priority is killed and rolled back?
    4) Is there an algorithm that kills the process that started first?
    Thanks
    Trev256, Mar 26, 2009
    #2

  2. FrankKalis Moderator

    +1 to remove this from the unanswered posts list.
    FrankKalis, Mar 27, 2009
    #3

  3. Trev256 New Member

    Sorry - what is the answer?
    Trev256, Mar 27, 2009
    #4

  4. satya Moderator

    Rather than adding up the long process to clear the issue why not find and resolve it, such as identify why deadlock occurss. BOL has got some information in this regard, check it out.
    satya, Mar 30, 2009
    #5

Share This Page