Consider the following scenario:
- You try to execute the sp_cursorprepare stored procedure to compile a cursor statement or batch into an execution plan in Microsoft SQL Server 2012.
- When the stored procedure does not return metadata for the cursor statement or batch, you execute the sp_describe_first_result_set stored procedure to receive the metadata for the expected result set of the Transact-SQL batch.
- The sp_describe_first_result_set stored procedure is called together with cursor-specific syntax. For example, you use a cursor statement in the stored procedure together with the FOR UPDATE clause.
In this scenario, you receive the following error message:
FOR UPDATE clause allowed only for DECLARE CURSOR.
- This issue also occurs when the sp_describe_undeclared_parameters stored procedure is called together with cursor-specific syntax.
- This issue occurs both server-side and client-side.
This issue occurs because the sp_cursorprepare
stored procedure cannot return metadata for a result set in SQL Server 2012.
After you apply the fix, the sp_cursorprepare
stored procedure can return metadata for a result set just as it functions in Microsoft SQL Server 2008 R2. Additionally, the fix adds retry logic so that SQL Server retries by using cursor-specific syntax when a stored procedure that has common syntax fails.
Cumulative update information
Cumulative update package 3 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative Update 3 for SQL Server 2012
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates