Microsoft KB Archive/913371

= FIX: You may receive error messages when you use the sp_cursoropen statement to open a cursor on a user-defined stored procedure in SQL Server 2005 =

Article ID: 913371

Article Last Modified on 7/26/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Express Edition
 * Microsoft SQL Server 2005 Workgroup Edition

-





''Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.''



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart your computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you use the sp_cursoropen statement to open a cursor on a user-defined stored procedure in Microsoft SQL Server 2005, you may receive the following error messages:

Msg 102, Level 15, State 1, Procedure, Line 5

Incorrect syntax near 'END'.

Msg 16945, Level 16, State 2, Procedure sp_cursoropen, Line 1

The cursor was not declared.

Note is a placeholder for the name of the user-defined stored procedure.

This problem occurs when all the following conditions are true:
 * One of the tables that are referenced by the user-defined stored procedure contains a relational index.
 * The sp_cursoropen statement has been executed, and the execution plan is already in the procedure cache.
 * The table that contains a relational index is modified by an index maintenance operation, such as the DBCC DBREINDEX statement or the ALTER INDEX statement.

For more information about execution plans, see the &quot;Execution plan caching and reuse&quot; topic in SQL Server 2005 Books Online.



Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Prerequisites
To apply this hotfix, you must have SQL Server 2005 installed on the computer.

Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry after you apply this hotfix.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2005, x64 versions
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.



WORKAROUND
To work around this problem, use one of the following methods:  Run the DBCC FREEPROCCACHE statement after the index of the table is modified.  Run the user-defined stored procedure with the WITH RECOMPILE clause. For example, you can use a statement that is similar to the following to open a cursor on a user-defined stored procedure that returns a result set. EXEC sp_cursoropen @c output, N'EXEC SP_Name WITH RECOMPILE' 



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 1.



Steps to reproduce the problem
Run the following Transact-SQL statements against the AdventureWorks database in SQL Server Management Studio. -- Create the user-defined stored procedure: CREATE PROCEDURE [ReindexProblem] AS BEGIN SELECT * FROM [AdventureWorks].[HumanResources].[Employee] END GO

-- Open a cursor on the stored procedure so that the execution plan is already in the procedure cache: DECLARE @c int SET @c = 0 EXEC sp_cursoropen @c output, N'EXEC [ReindexProblem]' EXEC sp_cursorclose @c GO

-- Reindex the table that is referenced by the stored procedure: DBCC DBREINDEX(N'[AdventureWorks].[HumanResources].[Employee]', N'', 90) GO

-- Then, run the procedure again: DECLARE @c int SET @c = 0 EXEC sp_cursoropen @c output, N'EXEC [ReindexProblem]' EXEC sp_cursorclose @c GO

