My @@version reports
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2811.0 (X64) Apr 6 2012 01:59:29 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
(However, ODDLY, the Setup Discovery Report, in installation center, titles itself “Microsoft SQL Server 2008 R2 SP1 Setup Discovery Report” and lists 10.51.2811.0 for all components(note the .51.))
http://support.microsoft.com/kb/321185 enumerates 10.50.2500.0 as Service Pack 1 and http://support.microsoft.com/kb/2567616 enumerates my version 10.50.2811 as CU6 which is what I have implemented…always applying SP1, then this CU around April of 2012. So I would strongly assert I am on SQL 2008 R2 Enterprise Edition SP1 plus CU6. Why the setup discovery report lists this as 10.51. instead of 10.50 just is a MS inconsistency in reporting.
My issue however is that I had hoped that CU6 would be one CU before the SP2 rollup, however, my timing was wrong*, and it was one ahead. SP2(July) was CU1-5(February 2012). SP2 was released in late July at http://blogs.msdn.com/b/sqlreleaseservices/archive/2012/07/26/sql-server-2008-r2-sp2-is-now-available.aspx but did not include April CU6.
MY MAIN QUESTION is what is the next best path for patching from SP1 plus CU6 on SQL 2008 R2(10.50.2811). Should I apply SP2(10.50.4000) and then maybe a SP2 CUx(but in a sense, I’m rolling back from CU6 to CU5 in that operation before I apply the SP2 CU) which will then put me on track again? This just seems a little dangerous for the registry/dll registrations/any updates to system objects in sql. OR should I accept that I am now out of sync so need to just apply latest CU for SP1 when needed and skip SP2 all together, and wait for SP3 to get back on track?
Thanks,
Forrest
*I was aggressive on patching because we did have one issue needing a CU, and living in a university network, aggressive security patching is also part of our life. I just happened to be going through a scheduled patching window at the same time MS was cutting over to SP2. Ugh.
UC Berkeley