{"id":1675,"date":"2019-08-11T09:18:50","date_gmt":"2019-08-11T16:18:50","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/glenn\/?p=1675"},"modified":"2020-08-04T17:09:36","modified_gmt":"2020-08-05T00:09:36","slug":"glenns-tech-insights-for-august-11-2019","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/glenn\/glenns-tech-insights-for-august-11-2019\/","title":{"rendered":"Glenn’s Technical Insights For August 11, 2019"},"content":{"rendered":"

(Glenn\u2019s Technical Insights\u2026<\/em> used to be part of our bi-weekly <\/span>newsletter<\/span><\/a> but we decided to make it a regular blog post instead so it can get more visibility. It covers interesting new hardware and software developments that are generally relevant for SQL Server).<\/span><\/p>\n

AMD Releases EPYC 7002 Series Processors<\/span><\/span><\/h2>\n

On August 7, 2019, AMD finally unveiled their new 7nm EPYC 7002 Series server processors, formally code-named \u201cRome\u201d at the AMD EPYC Horizon Event<\/a>. This is the second generation EPYC server processor that uses the same Zen 2 architecture as the AMD Ryzen 3000 series desktop processors. These new processors are socket compatible with the previous generation AMD EPYC 7001 processors, but you will need a new model server to be able to leverage PCIe 4.0 support.<\/span><\/p>\n

This new series includes 19 public launch SKUs that have anywhere from 8 physical cores to 64 physical cores. 2nd Generation AMD EPYC processors deliver up to 23% more instructions per clock (IPC) per core on server workloads and up to a 4X larger L3 cache compared to the previous generation AMD EPYC 7001 Series \u201cNaples\u201d processors.<\/span><\/p>\n

There is already very broad industry support behind these new processors, with Dell EMC, HPE<\/a>, Gigabyte, Lenovo<\/a>, SuperMicro<\/a>, and TYAN announcing new server models for these processors. Google is already using AMD EPYC 7002 processors<\/a> for internal infrastructure workloads and will be offering virtual machines using these processors later in 2019. Microsoft is offering<\/a> HBv2 virtual machines that will running on AMD EPYC 7002 series processors.<\/span><\/p>\n

The initial reviews and benchmarks have been very impressive.<\/span><\/p>\n

AMD EPYC 7002 Series Rome Delivers a Knockout<\/a><\/span><\/p>\n

AMD Rome Second Generation EPYC Review: 2x 64-core Benchmarked<\/a><\/span><\/p>\n

A detailed look at AMD\u2019s new Epyc \u201cRome\u201d 7nm server CPUs<\/a><\/span><\/p><\/blockquote>\n

This processor series is going to have a huge impact on the server market. I\u2019ll be writing a lot more about this in the future!<\/span><\/p>\n

\u00a0<\/span><\/p>\n

SQL Server 2016 and SQL Server 2017 Cumulative Updates<\/span><\/span><\/h2>\n

On July 31, 2019, Microsoft released SQL Server 2016 SP2 CU8<\/a> (Build 13.0.5426.0) which has 28 public hotfixes. If you are on SQL Server 2016, you really<\/strong><\/u> should be on the SP2 branch by now, especially since both the RTM and SP1 branches are no longer supported by Microsoft. If you are on the RTM or SP1 branch, you will have to install SP2, and then install the latest SP2 Cumulative Update to get fully up to date. I\u2019ve already updated my blog post that highlights the more important hotfixes (in my opinion) for each CU in the SP2 branch.<\/span><\/p>\n

Performance and Stability Related Fixes in Post-SQL Server 2016 SP2 Builds<\/span><\/a><\/p><\/blockquote>\n

On August 1, 2019, Microsoft released SQL Server 2017 CU16<\/a> (Build 14.0.3223.3) which has 39 public hotfixes. Starting with SQL Server 2017, Microsoft is not using Service Packs as a servicing mechanism for SQL Server<\/a>, only Cumulative Updates. Microsoft has fixed hundreds of bugs since SQL Server 2017 RTM, and they have also added a significant number of product improvements and new features since the RTM release. I\u2019ve already updated my blog post that highlights the more important hotfixes (in my opinion) for each SQL Server 2017 CU that has been released.<\/span><\/span><\/p>\n

Performance and Stability Fixes in SQL Server 2017 CU Builds<\/span><\/a><\/p><\/blockquote>\n

You really are better off trying to stay as current as possible on your SQL Server builds. Here is Microsoft\u2019s official guidance:<\/span><\/p>\n

Microsoft recommends ongoing, proactive installation of CUs as they become available<\/span><\/p>\n