FIX: A Cursor in a St. Procedure Can Cause an Access Violation |
Q141541
The information in this article applies to:
- Microsoft SQL Server version 6.0
BUG# NT: 11508 (6.00)
SYMPTOMS
A stored procedure that contains a cursor can cause an access violation if the following conditions are met:
- The cursor needs to have an expression clause.
- The cursor must have an ORDER BY clause.
- The stored procedure must be executed, dropped, recreated, and executed again for the AV to occur.
WORKAROUND
Remove or change the expression clause to not be an expression clause. Remove the ORDER BY and do the sort another way using temporary tables, or sort the result set on your client. Do not drop the stored procedure and immediately recreate and execute it. If the stored procedure must be dropped, then drop the stored procedure and shut down and restart SQL Server; this will allow it to execute upon re-creation.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem was corrected in Service Pack 2 for SQL Server version 6.0. For more information, contact your primary support provider.
Additional query words: sql6 av client
Keywords : kbusage
Issue type : kbbug
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600
Last Reviewed: March 25, 2000 |
