Could someone explain the SQL updates please? There’s SQL 2016 SP1 CU7 and SQL 2016 SP1 GDR
I get that we download the Security Update for CU7 if we have that particular cumulative update installed, but what if its CU4 or CU5? Do we use the GDR update? Or is that only for SQL 2016 SP1 that have had NO CU applied at all? BRIAN ILLNER | Canal Insurance Company 864.250.9227 864.679.2537 Fax [cid:[email protected]] Visit canalinsurance.com<http://canalinsurance.com> for news and information. [cid:[email protected]]<https://www.linkedin.com/company/canal-insurance-company> WARNING: As the information in this transmittal (including attachments, if any) may contain confidential, proprietary, or business trade secret information, it should only be reviewed by those who are the intended recipients. Unless you are an intended recipient, any review, use, disclosure, distribution or copying of this transmittal (or any attachments) is strictly prohibited. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal. While Canal believes this transmittal to be free of virus or other defect, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Canal (or its subsidiaries and affiliates) for any loss or damage arising therefrom. From: [email protected] [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Monday, January 8, 2018 10:46 AM To: [email protected] Subject: Re: [mssms] RE: Spectre/Meltdown patch breaks ConfigMgr/SQL? Based on how I 'interpreted' that tweet, it was specific regarding the SQL patch. In my case, the one I would care about is SQL 16 SP1, the CU7 (Cumulative Update 7). ConfigMgr requires "CLR" to be enabled in order to function. Additionally, the majority of environments except for a super small ones where they might only have ONE server with all roles--almost everyone has at least a MP, DP, or SUP role server elsewhere. Depending on the configuration of those other servers, they likely leverage a SQL 'thing' called Linked Servers. CU7 also modifies Linked server configuration. So just wait on deploying CU7 until further information is available. If you haven't yet gone to SQL 16 SP1 CU6, my understanding is that version is supported/acceptable to SCCM--but it obviously doesn't address the Spectre/Meltdown stuff. On Mon, Jan 8, 2018 at 8:25 AM, John Aubrey <[email protected]<mailto:[email protected]>> wrote: I THINK, there is a SQL patch as well as the Window patches. I applied the Windows patch had SCCM is still working. I think the SQL patch is the one that causes issues. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Mike Murray Sent: Friday, January 5, 2018 7:16 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Spectre/Meltdown patch breaks ConfigMgr/SQL? Could someone expand on this? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Richard Poole Sent: Friday, January 5, 2018 12:59 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Spectre/Meltdown patch breaks ConfigMgr/SQL? Thank you, Richard Poole From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mike Murray Sent: Friday, January 5, 2018 11:55 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Spectre/Meltdown patch breaks ConfigMgr/SQL? Anyone have issues with this? https://twitter.com/djammmer/status/949122372384141312<https://twitter.com/djammmer/status/949122372384141312> Mike NOTICE: This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message. This email neither constitutes an agreement to conduct transactions by electronic means nor creates any legally binding contract or enforceable obligation in the absence of a fully signed written contract. -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blog: http://mnscug.org/blogs/sherry-kissinger<http://mnscug.org/blogs/sherry-kissinger>
