Article ID: 48712 - View products that this article applies to.
This article was previously published under Q48712
This article has been archived. It is offered "as is" and will no longer be updated.
In SQL Server, an application attempting to access data that is locked by another user will be blocked until the lock is released. If this causes a deadlock (both requesting locks that the other holds), SQL Server will immediately terminate one of the participants (no timeout is involved).
If there is no deadlock, the application requesting the locked data will be blocked until the other user chooses to release the lock. There is no mandatory timeout period, and there is no way to test whether or not a data item is locked, except to attempt to access the data (and potentially get blocked indefinitely).
With DB-Library (DB-Lib), it is possible to continue issuing commands after a timeout has occurred. To regain control after a timeout period, do the following:
Article ID: 48712 - Last Review: February 27, 2014 - Revision: 3.1