Microsoft KB Archive/45548

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:56, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

INF: Detecting Deadlocks

ID: Q45548



The information in this article applies to:

  • Microsoft SQL Server for OS/2, version 4.2



SQL Server cannot detect deadlocks by simple timeout. SQL Server keeps track of which locks belong to which processes. When a request for a lock is blocked by another process that already holds a lock on that object, SQL Server checks to see if that other process is waiting for a lock that belongs to this process. In fact, it checks all waiting processes so that even transitive deadlocks are detected.

Deadlock does not refer to one transaction waiting for another to release a lock; it refers to a closed loop of waiting processes. Because it is impossible for any of the processes to ever complete, a timeout period makes no sense. Once the condition is detected, the process with the least amount of time invested is terminated.

Keywords : kbusage SSrvServer
Version : 4.2
Platform : OS/2
Issue type :


Last Reviewed: March 6, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.