SQL Server 2017 Cumulative Update 30

SQL Server 2017 Cumulative Update 30

On July 14th, 2022, Microsoft released SQL Server 2017 Cumulative Update 30. This is Build 14.0.3451.2. By my count, there are 8 public hotfixes and improvements in SQL Server 2017 CU30, which is a lower-than-average number. SQL Server 2017 is very mature now, so the number of hotfixes is quite low now.

Based on recent history, this might be the last CU before SQL Server 2017 falls out of mainstream support on October 11, 2022. Microsoft is supposed to release a SQL Server CU every eight weeks, but they have been struggling to hit that cadence over the past year.

SQL Server 2017 Cumulative Update 30
SQL Server 2017 Build Versions

No Service Packs

SQL Server 2017 and newer does not have Service Packs. Microsoft is no longer using Service Packs as a servicing mechanism for SQL Server, only cumulative updates.

SQL Server 2017 Cumulative Update 30
SQL Server Support End Dates

Due to human malware concerns, CU21 was delayed until July 1, 2020. SQL Server 2017 CU22 was released on September 10th, 2020. Since CU23, Microsoft seems to be back on a normal release schedule.

Normally, Microsoft will release a new SQL Server 2017 CU every two months. This is what they are supposed to do until SQL Server 2017 falls out of Mainstream Support on October 11, 2022. When SQL Server 2017 falls out of Mainstream Support, there won’t be any more cumulative updates. There will only be security updates while it is in Extended Support.

Final Words

SQL Server cumulative updates are actually cumulative, which might seem obvious from the name. This means that when you install SQL Server 2017 CU30, you are going to get all of the hotfixes and product improvements from ALL of the previous CUs. 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.

Despite some recent stumbles by Microsoft, I am still a big proponent of trying to keep your SQL Server instances as up to date as possible. That does not mean throwing a new CU into Production the day it is released, but it also does not mean avoiding patching SQL Server indefinitely either. You really are better off trying to stay as current as possible on your SQL Server builds.

Here is Microsoft’s official guidance:

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.

If you have any questions about this post, please ask me here in the comments or on Twitter. I am pretty active on Twitter as GlennAlanBerry. Thanks for reading!

Categories Cumulative Updates, SQL Server 2017Tags , ,

Please tell me what you think

search previous next tag category expand menu location phone mail time cart zoom edit close