Some SQL Server 2005 builds you may have missed (update: 2006-12-20)

Now that SQL Server 2005 is over a year old (what a big boy you are!), the beta builds are irrelevant, but the post-RTM builds fix some issues that may be quite important to you. If you want database mirroring, for example, this feature was not supported until SP1.

What follows is the list of builds since the latest entry at the URL above. If you're familiar with these build numbers, you probably know the drill — run SELECT @@VERSION; and if you don't recognize the build number returned (RTM is 9.00.1399.06; SP1 is 9.00.2047), then it will hopefully be in one of these two lists.

Build # KB # Title Date
9.00.3033 N/A December CTP for Service Pack 2 2006-12-19
9.00.3027 N/A November CTP for Service Pack 2 2006-11-08
9.00.2206 928539 FIX: An access violation is logged in the SQL Server Errorlog file when you … 2006-12-12
9.00.2198 924808 FIX: You receive an error message, or you obtain an incorrect result when you… 2006-12-13
9.00.2198 926611 FIX: SQL Server 2005 may not send a message notification that is… 2006-11-28
9.00.2198 926773 FIX: Error message when you run a query that uses a fast forward… 2006-11-16
9.00.2196 926335 FIX: Error message when you trace the Audit Database Management … 2006-12-05
9.00.2196 926285 FIX: Error message when you convert a column from the varbinary(… 2006-11-10
9.00.2194 925744 FIX: Error message when you try to use a SQL Server authenticate… 2006-10-20
9.00.2192 925335 FIX: Error message when you use a label after a Transact-SQL que… 2006-10-05
9.00.2192 924954 FIX: Error message when you use a table-valued function (TVF) to… 2006-09-29
9.00.2190 925227 FIX: Error message when you call the SQLTables function against … 2006-10-16
9.00.2189 925153 FIX: You may receive different date values for each row when you… 2006-09-22
9.00.2187 924601 FIX: A partitioned table may generate an inefficient query plan … 2006-09-29
9.00.2187 923849 FIX: When you run a query that references a partitioned table in… 2006-09-22
9.00.2181 922638 FIX: An EXCEPTION_STACK_OVERFLOW exception may occur when you tr… 2006-10-20
9.00.2181 923624 FIX: Error message when you run an application against SQL Serve… 2006-10-04
9.00.2176 923296 FIX: Log Reader Agent fails, and an assertion error message is l… 2006-09-06
9.00.2175 922438 FIX: A query may take a long time to compile when the query contains … 2006-12-14
9.00.2175 919839 FIX: The Distribution Agent may not apply transactions when you … 2006-10-18
9.00.2175 922296 FIX: You may receive an access violation error message when you … 2006-09-08
9.00.2164 919929 FIX: Error message when the Replication Merge Agent runs in SQL … 2006-10-26
9.00.2164 920206 FIX: System performance may be slow when an application submits … 2006-09-26
9.00.2164 920347 FIX: The SQL Server 2005 query optimizer may incorrectly estimat… 2006-09-19
9.00.2164 920346 FIX: SQL Server 2005 may overestimate the cardinality of the JOI… 2006-09-19
9.00.2164 918882 FIX: A query plan is not cached in SQL Server 2005 when the text… 2006-09-06
9.00.1551 922804 FIX: After you detach a Microsoft SQL Server 2005 database that … 2006-11-22
9.00.1551 922527 FIX: Error message when you schedule some SQL Server 2005 Integr… 2006-10-05

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. :-)

5 Responses

  1. SSB says:

    better source:
    Microsoft SQL Server 2005, 2000 and 7.0 Builds:

  2. AaronBertrand says:

    Well, I think (2) is only required if you are suffering from a symptom that is fixed by the specific hotfix, and you have talked it over with PSS.

    In general, hotfixes are not fully and thoroughly regression tested with the rigor that is applied to fully released service packs and cumulative hotfix packages.

    So, you shouldn't just apply the latest hotfix, simply because it exists.  Hotfixes are meant to fix specific problems, and should only be used once they have been tested and proven in a real world environment (read: not your desktop) to both fix the existing issue, and to not cause any others.

  3. Ashish says:

    Aaron so the process is

    1) Apply latest Service Pack
    2) Apply latest hot fix from the list.

    If the latest hot fix has some requirements of previous hot fixes it will throw an error and then you can apply the one listed in the error message before applying the latest.


  4. Aaron says:

    Most hotfixes and service packs are cumulative. There are a few exceptions; for example, in SQL Server 2000, there was an update to the hotfix installer (I forget which build #) which was required for all subsequent updates.  And I would definitely consider installing the latest full and released service pack, in 2000 or 2005, before applying a later hotfix (because I am not 100% confident that all hotfixes are designed to be applied directly to RTM).
    Since most non-general-release hotfixes require a conversation with Product Support Services, in those cases, you should talk with them about your current build # and whether it will require any other preparation before applying the hotfix.

  5. Ashish says:

    Does new build will contains all the previous build?

    I mean can I install the the latest build from the list and all the previous patches will automatically will be applied.