Further to this, I see CU1 for SP3 has subsequently been released but it's a 
bit different.

Previously, I've always been undecided on CU installs, namely because MS seem 
to have treated them as hotfixes with notes like this:


*         We recommend that you test hotfixes before you deploy them in a 
production environment.

*         We recommend that you apply the most recent update 
release<https://support.microsoft.com/en-us/kb/2772858> .

*         This cumulative package is intended to correct only the problems that 
are described in this article. Apply it only to systems that are experiencing 
these specific problems.

*         The most recent update 
release<https://support.microsoft.com/en-us/kb/2772858> contains all the 
hotfixes and all the updates that were included with the previous SQL Server 
2012 update release.
We recommend that you upgrade your SQL Server to the latest SQL Server 2012 
service pack<https://support.microsoft.com/en-us/kb/2755533>.

However, when I review the article for CU1 for SP3, it seems there's been a 
change of course and the aforementioned notes have been replaced with the 
following:


*         Each new Cumulative Update (CU) contains all the fixes that were 
included with the previous CU for the installed version/Service Pack of SQL 
Server.

*         Microsoft recommends ongoing, proactive installation of CUs as they 
become available:

*         SQL Server CUs are certified to the same levels as Service Packs, and 
should be installed at the same level of confidence.

*         Historical data shows that a significant number of support cases 
involve an issue that has already been addressed in a released CU.

*         CUs may contain added value over and above hotfixes. This includes 
supportability, manageability, and reliability updates.

*         Just as for SQL Server service packs, we recommend that you test CUs 
before you deploy them to production environments.

*         We recommend that you upgrade your SQL Server installation to the 
latest SQL Server 2012 service 
pack<https://support.microsoft.com/en-us/kb/3133750>.
Personally, this gives me the confidence to maintain the CU for my ConfigMgr 
site's SQL Server installation going forward.

Daniel.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Corkill, Daniel
Sent: Thursday, 28 January 2016 10:50 AM
To: [email protected]
Subject: [mssms] RE: SCCM and SQL SP3?

I see SP3 for SQL 2012 is now listed as supported. Has anyone upgraded? Any 
issues?

Daniel.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Mote, Todd
Sent: Wednesday, 2 December 2015 9:10 AM
To: '[email protected]' <[email protected]>
Subject: [mssms] RE: SCCM and SQL SP3?

That's kind of where I ended up too, I mean SP3 was just released last week, so 
I can't expect support for that yet, but CU9 for SP2 was only released the week 
before SP3, so....  I guess it's great to have "minimum supported", but it 
might be nice to have "maximum supported"?

Todd

From: [email protected] [mailto:[email protected]] On 
Behalf Of Corkill, Daniel
Sent: Tuesday, December 1, 2015 4:59 PM
To: [email protected]
Subject: [mssms] RE: SCCM and SQL SP3?

Todd,

I believe this has been discussed on this list before and my recollection is 
the consensus was that you cannot run any service pack beyond what is 
documented as supported but for the CU, you just had to be running the minimum 
supported. So until SP3 is supported, you should be able to run SP2 CU9 as a 
supported configuration. Hopefully someone else can confirm.

Daniel.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Mote, Todd
Sent: Wednesday, 2 December 2015 12:54 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] SCCM and SQL SP3?

So I'm tired of having to set IE in compatibility mode to look at SSRS reports 
so in looking it up, I found that that's been addressed in CU8 for SP1.  We 
have SQL 2012 SP1, currently.  I found trusty 
https://technet.microsoft.com/en-us/library/gg682077.aspx , but it really only 
lists minimums, and for SQL 2012, the highest minimum looks to be SP2 no CU.

My question is, is SP3 supported? Or is CU9 for SP2 ok?, or do I just stay with 
SP2 no CU?

Todd






*********************************************************************

This email, including any attachment, is confidential to the intended 
recipient.  It may also be privileged and may be subject to copyright.  If you 
have received this email in error, please notify the sender immediately and 
delete all copies of the email.  Any confidentiality or privilege is not 
waived.  Neither the Council nor the sender warrant that this email does not 
contain any viruses or other unsolicited items.



This email is an informal Council communication.  The Council only accepts 
responsibility for information sent under official letterhead and duly signed 
by, or on behalf of, the Chief Executive Officer.



Privacy Collection Notice

Logan City Council may collect your personal information, e.g. name, 
residential address, phone number etc, in order to conduct its business and/or 
meet its statutory obligations. The information will only be accessed by 
employees and/or Councillors of Logan City Council for Council business related 
activities only. If your personal information will be passed onto a third 
party, Council will advise you of this disclosure, the purpose of the 
disclosure and reason why. Your information will not be given to any other 
person or agency unless you have given us permission or we are required by law.









*********************************************************************

This email, including any attachment, is confidential to the intended 
recipient.  It may also be privileged and may be subject to copyright.  If you 
have received this email in error, please notify the sender immediately and 
delete all copies of the email.  Any confidentiality or privilege is not 
waived.  Neither the Council nor the sender warrant that this email does not 
contain any viruses or other unsolicited items.



This email is an informal Council communication.  The Council only accepts 
responsibility for information sent under official letterhead and duly signed 
by, or on behalf of, the Chief Executive Officer.



Privacy Collection Notice

Logan City Council may collect your personal information, e.g. name, 
residential address, phone number etc, in order to conduct its business and/or 
meet its statutory obligations. The information will only be accessed by 
employees and/or Councillors of Logan City Council for Council business related 
activities only. If your personal information will be passed onto a third 
party, Council will advise you of this disclosure, the purpose of the 
disclosure and reason why. Your information will not be given to any other 
person or agency unless you have given us permission or we are required by law.




*********************************************************************
This email, including any attachment, is confidential to the intended 
recipient.  It may also be privileged and may be subject to copyright.  If you 
have received this email in error, please notify the sender immediately and 
delete all copies of the email.  Any confidentiality or privilege is not 
waived.  Neither the Council nor the sender warrant that this email does not 
contain any viruses or other unsolicited items.

This email is an informal Council communication.  The Council only accepts 
responsibility for information sent under official letterhead and duly signed 
by, or on behalf of, the Chief Executive Officer.

Privacy Collection Notice
Logan City Council may collect your personal information, e.g. name, 
residential address, phone number etc, in order to conduct its business and/or 
meet its statutory obligations. The information will only be accessed by 
employees and/or Councillors of Logan City Council for Council business related 
activities only. If your personal information will be passed onto a third 
party, Council will advise you of this disclosure, the purpose of the 
disclosure and reason why. Your information will not be given to any other 
person or agency unless you have given us permission or we are required by law.



Reply via email to