Some new or updated SQL Server 2005 builds

Sorry, this table looks much better in preview mode than publish mode <shrug>. 

KB Title Build #
KB #932557 FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1399 1406
KB #932556 FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 1500 and later builds 1561
KB #932555 FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 2047 2050
KB #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" 2214
KB #931843 FIX: SQL Server 2005 does not reclaim the disk space that is allocated to the temporary table if the stored procedure is stopped 2218
KB #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" 2219
KB #932115 FIX: The ghost row clean-up thread does not remove ghost rows on some data files of a database in SQL Server 2005 2219
KB #931593 FIX: A script task or a script component may not run correctly when you run an SSIS package in SQL Server 2005 build 2153 and later builds 2221
KB #932990 FIX: You cannot obtain statements in the current batch in SQL Server 2005 by using the DBCC INPUTBUFFER statement, trace flag 1204, deadlock graph event class, or Activity Monitor 2224
KB #934066 FIX: The row of data on the publisher and the row of data on the subscriber may be inconsistent in a merge publication after synchronization has occurred in SQL Server 2005 2227
KB #934458 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 3042 through 3053 3054
KB #933564 FIX: A gradual increase in memory consumption for the USERSTORE_TOKENPERM cache store occurs in SQL Server 2005 3153
KB #934106 FIX: SQL Server 2005 database engine generates failed assertion errors when you use the Replication Monitor to monitor the distribution database 3154
KB #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 3154
KB #934188 FIX: The Distribution Agent does not deliver commands to the Subscriber even if the Distribution Agent is running in SQL Server 2005 3154
KB #933549 FIX: You may receive an access violation when you perform a bulk copy operation in SQL Server 2005 3155
KB #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)" 3155
KB #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)" 3156
KB #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 3159
KB #935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available 3161

Aaron Bertrand

I am a passionate technologist with industry experience dating back to Classic ASP and SQL Server 6.5. I am a long-time Microsoft MVP, write at SQLPerformance and MSSQLTips, and have had the honor of speaking at more conferences than I can remember. In non-tech life, I am a father of two, a huge hockey and football fan, and my pronouns are he/him. If I've helped you out, consider thanking me with a coffee. :-)

1 Response

  1. Scott Whigham says:

    Thanks for keeping this up to date, Aaron. I can point clients to this list and help them keep up to date w/o having to wade through all the MSFT mucky-muck to figure out what they need.