This time it's for real – SQL Server 2008 Service Pack 2 is available!
September 29th, 201013
This time it's for real – SQL Server 2008 Service Pack 2 is available!
September 29th, 201013

I'm not going to blab about the speculation, or how Microsoft seems to like making their promised deadlines by the skin of their teeth.  I'm too busy preparing how we're going to deploy and test SP2 on all of our SQL Server 2008 instances.  So without any delay, here are the downloads / fix information:

Download Details: Microsoft SQL Server 2008 Service Pack 2

KB #2285068 : List of the bugs that are fixed in SQL Server 2008 Service Pack 2

As we've seen before, the release has been quietly posted to the downloads site and knowledge base with little fanfare, and there is not yet a post on the SQL Server Release Services blog.  But I'm sure you'll hear more about it soon.

Note that the Service Pack only includes the fixes that were in SP1 CU 1 through 8.  So if you have already applied CU9 or CU10, I would hold off on deploying the service pack for now, especially if you are relying on any of the fixes in either of those CUs – because there is a chance that you will lose them.

The service pack will patch any existing SQL Server 2008 instances (and client tools) on your machine, including Express instances (I seem to remember that you used to have to patch Express instances separately, with the whole Express setup program).  Note that you can't patch client tools with a SQL Server 2008 Service Pack if you already have SQL Server 2008 R2 tools installed – this just means that the Shared Tools checkbox will be unavailable.

I know that some of you like to hear about the build numbers more than anything else.  This service pack will move your build number to 10.0.4000:


Fellow SQL Server MVP Denis Gobo (blog | twitter) spoke about some of the changes introduced with Service Pack 2.

EDIT: And here are the announcements from the SQL Server Team Blog and SQL Server Release Services blog.

By: 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 Simple Talk, SQLPerformance, and MSSQLTips, and have had the honor of speaking at more conferences than I can remember. In non-tech life, I am a husband, a father of two, a huge hockey and football fan, and my pronouns are he/him.

13 Responses

  1. Aaron Bertrand says:

    Sorry KP, don't know how to help you.  Is this ReportViewer / C# problem documented in a public KB article or Connect item?

  2. Sharee-Lee says:

    Thanks guys for the tips it was very useful.

  3. KP says:

    This service pack can not resolved my work in ReportViewer control on C#.NET using local mode.

  4. AaronBertrand says:

    I hear you.  When you find it, let me know.  If I find it first, you'll see it here!

  5. Imtiaz says:

    Thanks Aaron, yes I came across that post too. Just looking for that Silver Bullet! 😉

  6. AaronBertrand says:

    Wish I had better news for you Imtiaz, but I still rely on a rather manual approach.  You may find this earlier blog post useful:

  7. Imtiaz says:

    I know this subject has come up a few times but wanted to see if there is any progress on it or a clever workaround?
    Release Notification from SQL Release Services:
    I have an RSS feed setup (Netvibes) and this is how I currently keep myself up-to-date with latest releases/cu's etc.
    However, what I really want (no not Twitter!) is the ability to download something, ANYTHING, which will allow me to know that there has been a release, regardless of the release, and then marry it up against my current SQL servers to see which ones 'could' be updated, or atleast report on which servers may be available for an update.
    In a multi-version environment, where cu's/sp's are multi version released, it would be nice to have my own database of these patches and notify me automatically when a patch is available.
    Any ideas/suggestions if this is possible today?

  8. AaronBertrand says:

    I've only installed it in a VM with an Express and a Workgroup instance.  Real testing will have to wait, I'm afraid.

  9. AaronBertrand says:

    Yes it is 4000.  It was pretty high in the 3xxx range, IIRC (3798 maybe?).

  10. Glenn Berry says:

    Have you installed it on a test box yet?  Did they really jump to Build 4000?  The CTP was in the 3xxx range.

  11. bender says:

    Thanks Aaron.  Just wanted to be sure.

  12. AaronBertrand says:

    No bender, this service pack has nothing to do with R2.  So many people get confused by this.  I wish they had just called it SQL Server 2010.  Like anyone would complain about too many "major" releases.  If it requires a new license, it's a major release for those willing to spend the money on the upgrade.

  13. bender says:

    So, would this apply to SQL Server 2008 R2?  Or only to SQL Server 2008?