On May 28, 2020, Microsoft released SQL Server 2016 SP2 CU13, which is Build 13.0.5820.1. By my count, there are 27 public hot fixes in this cumulative update. As of the time of this post, only eight of the hotfixes have links to KB articles. This is very unusual.
Normally, every single hot fix has a KB article with more information about the problem and the fix. Sometimes, the KB documentation is pretty sparse, but it is at least there. I am guessing that this issue is caused by the current human malware situation, and the impact that has caused for normal work procedures.
Cumulative Update Delays
Microsoft previously announced that SQL Server 2016 SP2 CU13 was going to be released in June, as I discussed here. Here is what they said:
Microsoft SQL Server 2019, 2017, 2016 Service Pack 2. Starting in May 2020, Microsoft will delay the release date for all mainstream supported SQL Server Cumulative Updates (CUs) out by one month. Currently, the specific CUs impacted by this change are: SQL Server 2019 CU5 (moved to June), SQL Server 2016 SP2 CU13 (moved to June), and SQL Server 2017 CU21 (moved to July).
I have always been a public, vocal supporter of the concept of trying to keep your SQL Server instances properly patched as much as possible. Ideally, that means being on the latest public build, as soon as you can test and deploy it.
That doesn’t mean throwing it into Production the day it is released, but it also doesn’t mean never patching your SQL Server instances. Every organization needs to find a testing and patching cadence that works for them. Being proactive about patching (meaning having a plan and actually executing it) is better than ignoring it completely.
What do you think? I would love to hear your thoughts in the comments and on Twitter. I am pretty active on Twitter as GlennAlanBerry. Thanks for reading!
2 thoughts on “SQL Server 2016 SP2 CU13 Released”
Do you think a serious situation came up that they couldn’t wait to release? Might explain the lack of KB documentation?
I honestly don’t know. Based on their previous guidance, they could have released on June 30th and still been “in June 2020”.