Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available

How to obtain the cumulative update package (build 3161) for SQL Server 2005 SP2
A supported hotfix is now 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 SQL Server 2005 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
http://go.microsoft.com/?linkid=6294451

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

50000786 An application that uses 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 update a view by using a cursor, error 16934 occurs. The error message for error 16934 is as follows: "Optimistic concurrency check failed. The row was modified outside of this cursor."

50000809 The lazywriter process may cause high CPU usage in SQL Server 2005 on a computer that has "non-uniform memory access" (NUMA) architecture.

50000874 The disk space that is allocated for temporary tables may not be released. This problem occurs when a temporary table is created on a connection that has the SET XACT_ABORT option set to ON.

50000889 In the Data Mining Client for Excel add-in, you perform the Analyze Key Influencers action against a SQL Server 2005 Analysis Services Standard Edition server. When you do this, you receive the following error message: "The 'MINIMUM_DEPENDENCY_PROBABILITY' data mining parameter is not valid for the 'ATableName' model."

50000921 A transactional replication publication that involves replicated procedure executions may cause error 701. The error message for error 701 is as follows: "There is insufficient system memory to run this query."

50000945 The USERSTORE_TOKENPERM SQL Server 2005 memory cache may grow too large. Therefore, high CPU utilization occurs, or "out of memory" errors occur.

50000964 SQL Server 2005 may select a poorly performing query plan for a query that references a scalar user-defined function that performs data access.

50000969 In SQL Server 2005, assertion error 3624 may occur. The error message for assertion error 3624 is as follows: "Attempt to access expired blob handle (3)."

50000918 When you run a query that uses the FOR XML clause together with the TYPE directive, the query may fail. Additionally, error 6611 may occur. The error message for error 6611 is as follows: "The XML data type is damaged."

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.

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."

50001026 After you perform a piecemeal restoration of a database that uses the vardecimal storage format, filegroups may be marked as defunct.

50001083 When you join an int data type column together with a bigint data type column, you may obtain incorrect results. This problem occurs if the join uses bitmap filtering.

50001076 Tables in SQL Server 2005 Reporting Services reports may not be displayed correctly when you view the reports in Microsoft Office Outlook 2007.

50001105 After you apply SQL Server 2005 SP2, the Print Preview feature in Reporting Services may show a solid black page.



Read more here: http://support.microsoft.com/kb/935356