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
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 SP_Name, Line 5
Incorrect syntax near 'END'.
Msg 16945, Level 16, State 2, Procedure sp_cursoropen, Line 1
The cursor was not declared.
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 "Execution plan caching and reuse" 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Â
(http://kbalertz.com/Feedback.aspx?kbNumber=913089/
)
How to obtain the latest service pack for SQL Server 2005
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
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, 32-bit versions
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Microsoft.sqlserver.smo.dll | 9.0.1518.0 | 1,559,256 | 20-Jan-2006 | 09:10 | x86 |
| Msxmlsql.dll | 2005.90.1518.0 | 899,638 | 20-Jan-2006 | 08:11 | x86 |
| Osql.exe | 2005.90.1518.0 | 51,416 | 20-Jan-2006 | 09:11 | x86 |
| Sqlaccess.dll | 2005.90.1518.0 | 349,400 | 20-Jan-2006 | 09:11 | x86 |
| Sqlservr.exe | 2005.90.1518.0 | 28,778,256 | 20-Jan-2006 | 09:11 | x86 |
SQL Server 2005, IA-64 versions
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Microsoft.sqlserver.smo.dll | 9.0.1518.0 | 1,551,064 | 20-Jan-2006 | 12:30 | x86 |
| Osql.exe | 2005.90.1518.0 | 123,096 | 20-Jan-2006 | 12:30 | IA-64 |
| Sqlaccess.dll | 2005.90.1518.0 | 351,448 | 20-Jan-2006 | 12:30 | x86 |
| Sqlservr.exe | 2005.90.1518.0 | 72,181,976 | 20-Jan-2006 | 12:31 | IA-64 |
SQL Server 2005, x64 versions
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Microsoft.sqlserver.smo.dll | 9.0.1518.0 | 1,551,064 | 20-Jan-2006 | 13:14 | x86 |
| Osql.exe | 2005.90.1518.0 | 83,672 | 20-Jan-2006 | 13:14 | x64 |
| Sqlaccess.dll | 2005.90.1518.0 | 356,568 | 20-Jan-2006 | 13:14 | x86 |
| Sqlservr.exe | 2005.90.1518.0 | 39,397,592 | 20-Jan-2006 | 13:14 | x64 |
Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
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'
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" 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
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499Â
(http://kbalertz.com/Feedback.aspx?kbNumber=822499/
)
New 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:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
For more information, see the following topics in SQL Server 2005 Books Online:
- System stored procedures (Transact-SQL)
- DBCC DBREINDEX (Transact-SQL)
- ALTER INDEX (Transact-SQL)
- EXECUTE (Transact-SQL)