Help and Support

Article ID: 58534 - Last Review: February 14, 2005 - Revision: 3.2

INF: Specifying Priority for Deadlock Victim Selection

This article was previously published under Q58534
Expand all | Collapse all

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.

APPLIES TO
  • Microsoft SQL Server 4.21a Standard Edition
  • Microsoft SQL Server 6.0 Standard Edition
  • Microsoft SQL Server 6.5 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbenv KB58534

Article Translations

 

Related Support Centers