INF: Specifying Priority for Deadlock Victim Selection

Last reviewed: April 25, 1997
Article ID: Q58534

The information in this article applies to:

  - Microsoft SQL Server, versions 4.2x and 6.0
  - Microsoft SQL Server, version 4.2 for OS/2

SUMMARY

In Microsoft SQL Server version 4.2x, when a deadlock condition occurs between two user-defined transactions, the transaction that has used more resources is allowed to continue and the other is rolled back.

In Microsoft SQL Server version 6.0, you can prioritize deadlock settings by using the SET DEADLOCK_PRIORITY statment. For more information on setting deadlock priority, see Microsoft SQL Server Books Online, "Transact- SQL Reference", the SET statement.

Additional query words: sql6 deadlock locking
Keywords : kbenv SSrvLock
Version : 4.2x 6.0 | 4.2
Platform : OS/2 WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.