BUG: Fetching from a Cursor with Existence Clause May Cause an Access Violation (184497)
The information in this article applies to:
- Microsoft SQL Server 6.5 Service Pack 3 and later
This article was previously published under Q184497
BUG #: 17591 (SQLBUG_65)
SYMPTOMS
Fetching from a cursor may generate a handled access violation (AV) and
the client may never receive any results or messages.
CAUSE
This problem can be caused when both of the following conditions are true:
- All tables involved in the FROM clause do not contain a unique index.
-and-
- The keywords EXISTS or NOT EXISTS are used in the WHERE clause.
WORKAROUND
To work around this problem, do any one of the following:
- Ensure that all tables involved in the FROM clause contain a unique
index.
-or-
- Change the cursor from a DYNAMIC to a SCROLL or INSENSITIVE cursor.
-or-
- Turn on trace flag 7501 to force the cursor to be resolved as a keyset
cursor.
STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5
Service Pack 3 and later. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.
Modification Type: | Major | Last Reviewed: | 10/3/2003 |
---|
Keywords: | kbBug kbpending KB184497 |
---|
|