Oct
6
2017
6
2017
Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
With SQL Server 2017 GA announcement for October-2 2017, Microsoft is introducing changes to the servicing model through GDRs, CUs and SPs.
Excerpt from article published:
—————————————–
The Modern Servicing Model
Starting with SQL Server 2017, we are adopting a simplified, predictable mainstream servicing lifecycle:
- SPs will no longer be made available. Only CUs, and GDRs when needed.
- CUs will now accommodate localized content, allowing new feature completeness and supportability enhancements to be delivered faster.
- CUs will be delivered more often at first and then less frequently. Every month for the first 12 months, and every quarter for the remainder 4 years of the full 5-year mainstream lifecycle.
- CUs are delivered on the same week of the month: week of 3rd Tuesday.
Note: the Modern Servicing Model (MSM) only applies to SQL Server 2017 and future versions.
Servicing lifecycle
The servicing lifecycle is unchanged for SQL Server 2016:
- Years 0-5 (Mainstream Support): Security and Functional issue resolution though CUs. Security issues through GDRs.
- Years 6-10 (Extended Support): Security or critical functional issues.
- Years 11-16 (Premium Assurance): Optional paid extension to Extended Support (no scope change).
—————————————–
You can read all about these changes in our blog post here, which includes an extensive FAQ section.

Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
80040e31
ACO5422E
agent not starting
AWE
cache
cluster
connection
datacollector
error
failure
lock pages in memory
maintenance plan
Maintenance plan error
microsoft
Migration
MSDTC
OLEDB error
outlook
RAM
Replication
Script
SQL2000
SQL agent
SQL login
sql server
SQLServer
SQL Server 2000
SQL Server 2005
SQL Server 2005 SP2
SQL Server 2008
SQLServer2008
SQL Server 2008 R2
SQL Server 2012
SQL Server Denali
t-sql
tdp sql v5.5.1
tdp v5.5.1
timeout error
tips
tivoli
Tivoli Data Protection
transactional replication
upgrade
Windows
x64
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5