First off, the less interesting one: SQL Server 2017 Cumulative Updates come out about every 60 days, so that one’s not a big deal. The new Cumulative Update 26 includes fixes for columnstore, affinity masking, and other stuff. Note that sp_pkeys was broken in CU25, and that one’s still not fixed in CU26.
Now for the more interesting one: SQL Server 2016 Service Pack 3.
2016 was the last version to have Service Packs. Starting with 2017, Microsoft only ships Cumulative Updates. In the past, Microsoft has used one last Service Pack to kinda seal the tomb, closing off support for a version. Long term support is only available for the last Service Pack for a product. As of today, 2016 SP2 only gets support until October 11, 2022, whereas SP3’s support goes all the way out through 2026.
I like this approach because it makes support simpler. Microsoft doesn’t have to deal with a wide variety of builds for these older versions (if you can call 2016 older) – we can just say, “If you want help, it’s gotta be build 13.0.6300.2.”
Sure, there are a list of fixes in the KB article, but for me, the bigger takeaway is that for long term support, you need to patch all your 2016 instances at some point in the near future. I know, it’s a little more work added to your plate – but ideally, this will be the last SQL Server patch you’ll ever have to apply on those boxes, barring a critical security surprise.
SQL Server 2016 isn’t dead yet, but…he did just have his retirement party and get a box with a nice gold watch for his services.
I’m one of the Support Escalation Engineers for SQL Server that work at Microsoft. I have received a case for the sp_pkeys issue and have engaged the SQL Server Product Group about it.
Thanks, that’s great to hear!
I mentioned that I’d raised this with the SQL Server Product Group. They have confirmed that it is a bug and are targeting a fix in SQL Server 2017 CU27.
I’m pleased to say the fix has been released in SQL Server 2017 CU27 – https://support.microsoft.com/en-gb/topic/kb5006944-cumulative-update-27-for-sql-server-2017-79117c8f-9d54-42f8-9727-5870fe475187.
When I tried to update SQL Server 2016 SP3 for a customer it stopped at the instance selection window and did not go any further. There were 3 instances on the server. 1 Prod instance, 1 Test instance and 1 DEV instance. There was neither any instance marked nor could I select 1 instance to update. When I clicked further it gave an error that no instance is selected. The last state of the SQL Server was CU17.
What did I do wrong. What is the error?
I wish I could do free production support for your customers, but your best bet there would be to contact Microsoft.