FIX: EventSubClass Column Incorrect for Deadlock Chain Events

Article translations Article translations
Article ID: 293632 - View products that this article applies to.
This article was previously published under Q293632
BUG #: 352735 (SHILOH_BUGS)
Expand all | Collapse all


In a SQL Server 2000 Profiler trace, the EventSubClass column in the Lock:DeadlockChain event may show incorrect information.


To resolve this problem, obtain the latest service pack for Microosoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


To determine the lock mode from a SQL Server 2000 Profiler trace, use the Mode column instead of the EventSubClass column. The values in the Mode column are integers; for a list of the possible integer values and the corresponding lock modes, see the documentation for the syslockinfo.req_mode column in the SQL Server Books Online topic "syslockinfo".


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 1.


The EventSubClass column in a Lock:DeadlockChain event is supposed to show the deadlock resource type. Before SQL Server 2000 Service Pack 1 (SP1), what appears in this column is a lock mode that is not related to the actual lock mode. For example, you may see "Schema Stability" when the actual lock mode is "Key". After SP1, the EventSubClass column correctly identifies the type of resource involved in the deadlock ("Lock", "Exchange", "Thread", or "Page Supplier").


Article ID: 293632 - Last Review: November 6, 2003 - Revision: 3.2
  • Microsoft SQL Server 2000 Standard Edition
kbbug kbfix kbsqlserv2000sp1fix KB293632

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from