FIX: Descending Index Scans May Block with High Transaction Isolation (196919)
The information in this article applies to:
This article was previously published under Q196919
BUG #: 52498
SYMPTOMS
A descending index scan with a SERIALIZABLE transaction isolation level or
a HOLDLOCK hint can hold a lock that prevents inserts greater than the
highest value current in the table for the index the scan is performed on.
WORKAROUND
To work around this problem, do not use descending index scans when using a
SERIALIZABLE transaction isolation level or a HOLDLOCK hint.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Modification Type: | Major | Last Reviewed: | 3/14/2006 |
---|
Keywords: | kbBug kbfix kbSQLServ700sp1fix KB196919 |
---|
|