Changes to the SQL Server Servicing Model (Cumulative Updates)
Changes to the SQL Server Servicing Model (Cumulative Updates)
Microsoft has announced changes to its servicing model for SQL Server. We examine them in this post.
Join the DZone community and get the full member experience.
Join For FreeMariaDB TX, proven in production and driven by the community, is a complete database solution for any and every enterprise — a modern database for modern applications.
On Monday of this week, Microsoft announced changes to the servicing model for SQL Server, starting with SQL Server 2017.
From today onward, we can expect to see the following during the first five years after release (known as Mainstream Support):
- One Cumulative Update per month for the first twelve months.
- One Cumulative Update every two months thereafter (bi-monthly), for two more years.
- After three years, this might change to a quarterly release cadence.
- There is no slipstream installation media included with the annual Cumulative Update.
Originally, the model was as follows:
- One Cumulative Update per month for the first twelve months.
- One Cumulative Update every three months thereafter, for four more years.
- The Cumulative Update would include a slipstreamed install, including all CUs to that point.
I am encouraged by Microsoft increasing the cadence for Cumulative Updates for the first three years, however I am slightly disappointed that the annual CUs don't include a slipstreamed installer. While I understand Microsoft's reasoning, it does mean having to maintain my own slipstreamed installation media, which may be something you need to consider doing as well. If you haven't made a slipstream of SQL Server before, I'll be covering how to do that in an upcoming post.
Leave your thoughts in the comments below.
MariaDB AX is an open source database for modern analytics: distributed, columnar and easy to use.
Like This Article? Read More From DZone
Published at DZone with permission of Randolph West , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}