Is my math right? The new CU servicing schedule for SQL Server 2017 is:
- 1 CU per month for the first year
- 1 CU per quarter through mainstream support (5 years)
That means by my count, we get this:
WITH myTally(n)
AS
(SELECT n = ROW_NUMBER() OVER (ORDER BY (SELECT null))
FROM (VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9), (10)) a(n)
CROSS JOIN (VALUES (1), (2), (3)) b(n)
)
SELECT dt = CAST('20171002' AS DATE)
, patch = 'RTM'
UNION
SELECT dt = DATEADD( MONTH, n, CAST('2017-10-02' AS date))
, patch = 'CU' + CAST(n AS VARCHAR(2))
FROM myTally
WHERE n < 12
UNION
SELECT dt = DATEADD( QUARTER, n-13, CAST('2018-10-02' AS date))
, patch = 'CU' + CAST((n -1) AS VARCHAR(2))
FROM myTally
WHERE n >12
AND n < 30
ORDER BY dt
Or, for those of you want want it spelled out:
2017-10-02 RTM
2017-11-02 CU1
2017-12-02 CU2
2018-01-02 CU3
2018-02-02 CU4
2018-03-02 CU5
2018-04-02 CU6
2018-05-02 CU7
2018-06-02 CU8
2018-07-02 CU9
2018-08-02 CU10
2018-09-02 CU11
2018-10-02 CU12
2019-01-02 CU13
2019-04-02 CU14
2019-07-02 CU15
2019-10-02 CU16
2020-01-02 CU17
2020-04-02 CU18
2020-07-02 CU19
2020-10-02 CU20
2021-01-02 CU21
2021-04-02 CU22
2021-07-02 CU23
2021-10-02 CU24
2022-01-02 CU25
2022-04-02 CU26
2022-07-02 CU27
2022-10-02 CU28
There will be slippage, and potentially other issues, so I don’t know we’ll see 28 CUs, but having a schedule is something I’m glad about.
Voice of the DBA 