SQL 2005 Patch Levels

  • I have a new SQL 2005 Cluster (Standard Edition 64-bit) with the initial installation (9.00.1399.06).

    After reading a couple of articles on Microsoft's web site I am a bit confused as to which SP or SP + Build #___ or SP + GDR ___ to apply.

    My older SQL 2005 server has SP2 plus GDR2 (9.00.3054).

    http://support.microsoft.com/kb/937137/LN/

    This one is a bit outdated but I like Bob Ward's candidness in the article:

    http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx

    I'm curious to see what patch level others are running. Thanks to those who respond.

  • I have been advising my clients to go to 3186 and stop there for now. I got some validation for that last night on the SQL MVP monthly topics call where one of the guys mentioned having significant problems with builds above that number, especially in clustered environments. I just picked up a new client that went to 3200 on one of their (clustered) production machines because they were getting demonstrated issues with one of the bugs fixed by that build. Wonder how that will work out.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • definitely seems like 3186 is the limit for x64 environments.

    I'd go SP2 + Cumulative updates if you have issues. Be sure you test this on another server to be sure it doesn't cause obvious problems, and stop at 3186 if you're clustered for now.

  • What about for those that are not on cluster? We are on 3054 now and considering whether we should apply any CU to the db or not.

    Our SQL Server 2005 is x64 enterprise.

    Thanks.

  • to confuse the issue security release MS08-040 is out which would take you to 3233 if you were already at 3186.

    http://www.microsoft.com/technet/security/Bulletin/MS08-040.mspx

    ---------------------------------------------------------------------

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply