How to obtain Cumulative Update 1 for SQL Server 2005 Service Pack 2
A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2005 service pack that contains the hotfixes in this cumulative update package.
If the cumulative update 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 cumulative update package.
Note If additional issues occur or 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 cumulative update package. 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 cumulative update is available. If you do not see your language, it is because a cumulative update package is not available for that language.
SQL Server 2005 post-SP2 hotfixes that are included in the cumulative update package (build 3161) for SQL Server 2005 SP2
Note Microsoft Knowledge Base articles that discuss these hotfixes will be released as the hotfixes become available.
For more information about the bugs, click the article numbers to view the articles in the Microsoft Knowledge Base.
| SQL Hotfix bug number | Knowledge Base article number | Description |
|---|
| 50000939 | 933508 | Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at different intervals than intended |
| 50000787 | 929240 | FIX: I/O requests that are generated by the checkpoint process may cause I/O bottlenecks if the I/O subsystem is not fast enough to sustain the IO requests in SQL Server 2005 |
| 50000784 | 930505 | FIX: Error message when you run DML statements against a table that is published for merge replication in SQL Server 2005: "Could not find stored procedure" |
| 50000783 | 930691 | FIX: SQL Server Profiler stops monitoring the instance after a time when you use SQL Server Profiler to monitor an instance of SQL Server 2005 Analysis Services |
| 50000785 | 930775 | FIX: Error message when you try to retrieve rows from a cursor that uses the OPTION (RECOMPILE) query hint in SQL Server 2005: "Could not complete cursor operation because the table schema changed after the cursor was declared" |
| 50000873 | 931329 | FIX: Error message when you run a query in Microsoft SQL Server 2005: "Msg 8624, Level 16, State 116 Internal Query Processor Error: The query processor could not produce a query plan" |
| 50000875 | 932115 | FIX: The ghost row clean-up thread does not remove ghost rows on some data files of a database in SQL Server 2005 |
| 50000900 | 933549 | FIX: You may receive an access violation when you perform a bulk copy operation in SQL Server 2005 |
| 50000949 | 934109 | FIX: The Distribution Agent generates an access violation when you configure a transactional replication publication to run an additional script after the snapshot is applied at the subscriber in SQL Server 2005 |
| 50000952 | 934188 | FIX: The Distribution Agent does not deliver commands to the Subscriber even if the Distribution Agent is running in SQL Server 2005 |
| 50000958 | 934226 | FIX: Error message when you try to use Database Mail to send an e-mail message in SQL Server 2005: "profile name is not valid (Microsoft SQL Server, Error 14607)" |
| 50001012 | 934459 | FIX: The Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context in certain circumstances in SQL Server 2005 builds 3150 through 3158 |
| 50000948 | 934106 | FIX: SQL Server 2005 database engine generates failed assertion errors when you use the Replication Monitor to monitor the distribution database |
| 50000684 | 931821 | FIX: High CPU utilization by SQL Server 2005 may occur when you use NUMA architecture on a computer that has an x64-based version of SQL Server 2005 installed |
| 50000769 | 931843 | FIX: SQL Server 2005 does not reclaim the disk space that is allocated to the temporary table if the stored procedure is stopped |
| 50000918 | 933808 | FIX: Error message when you run a query that contains nested FOR XML clauses in SQL Server 2005: "The XML data type is damaged" |
| 50000921 | 933499 | FIX: Error message when you use transactional replication to replicate the execution of stored procedures to subscribers in SQL Server 2005: "Insufficient memory to run query" |
| 50000945 | 933564 | FIX: A gradual increase in memory consumption for the USERSTORE_TOKENPERM cache store occurs in SQL Server 2005 |
| 50000964 | 933724 | FIX: The query performance is slow when you run a query that uses a user-defined scalar function against an instance of SQL Server 2005 |
| 50000969 | 933766 | FIX: Failed assertion message in the Errorlog file when you perform various operations in SQL Server 2005: "Failed Assertion = 'fFalse' Attempt to access expired blob handle (3)" |
| 50001026 | 934706 | FIX: Error message when you perform a piecemeal restore operation after you enable vardecimal database compression in SQL Server 2005 Service Pack 2: "Piecemeal restore is not supported when an upgrade is involved" |
| 50001076 | 935399 | FIX: A table in a report that is delivered by SQL Server 2005 Reporting Services with Service Pack 2 appears to be compressed when the report is opened in Outlook 2007 |
| 50001083 | 935789 | FIX: On a computer that is running SQL Server 2005 and that has multiple processors, you may receive incorrect results when you run a query that contains an inner join |
| 50001105 | 935436 | FIX: The background color of a report may be black when the report is hosted by a report server in SQL Server 2005 Reporting Services |
| 50000786 | | An application that uses the Analysis Services 9.0 OLE DB Provider (Msolap90.dll) to connect to SQL Server 2005 Analysis Services may experience a memory leak. |
| 50000810 | | When you use a cursor to update a view, error 16934 occurs. The error message for error 16934 is as follows: "Optimistic concurrency check failed. The row was modified outside of this cursor." |
| 50000889 | | In the Data Mining Client for Excel add-in, you perform the Analyze Key Influencers action against a server that is running SQL Server 2005 Analysis Services Standard Edition. When you do this, you receive the following error message: "The 'MINIMUM_DEPENDENCY_PROBABILITY' data mining parameter is not valid for the 'ATableName' model." |
| 50000919 | | When you run an encrypted stored procedure, error 565 may occur. The error message for error 565 is as follows: "A stack overflow occurred in the server while compiling the query. Please simplify the query." |
| 50000960 | | A content query from the Data Mining Client for Excel add-in may take a long time to display the result set. This problem occurs especially when the result set is large. Microsoft Office Excel may appear to stop responding (hang) when the query is running. |