SQL Server 2017 Gets Cumulative Update 15 (KB4498951): What's New?

Table of Contents

Hey SQL Server fans! Get ready for a dose of awesome updates because CU15 for SQL Server 2017 has arrived, and it’s bringing a whole bunch of fixes and improvements. Released on May 23, 2019, this update is packed with goodies to make your SQL Server experience even smoother. Let’s dive in!

image just illustration

What’s New in SQL Server 2017 CU15?¶

This Cumulative Update, version 14.0.3162.1, addresses 44 fixes that cropped up after CU14. It updates several key components to the following builds:

• SQL Server: Product version 14.0.3162.1, file version 2017.140.3162.1
• Analysis Services: Product version 14.0.249.3, file version 2017.140.249.3

And the best part? No known issues! High five!

Need a Build Summary and Support Lifecycle Info?¶

Microsoft has you covered. A downloadable Excel workbook summarizing builds and their support lifecycles is ready and waiting for you. It also includes detailed fix lists for SQL Server 2019 and 2017. Grab it here: Download Excel File.

Bookmarkable Bug Fixes!¶

You can now directly link to specific fixes in the table below. Just click a bug reference ID, and a bookmark tag (#NNNNNNNN) will be added to the URL. Share this customized link to help others jump straight to the relevant fix. How cool is that?

Improvements and Fixes Included in This Update¶

This table lists the Knowledge Base articles detailing the bugs squashed and enhancements included in CU15. Click the bug reference to jump directly to the relevant Microsoft support article.

Bug Reference	Description	Fix Area	Component	Platform
12745584	FIX: Exception occurs when you design a parameterized DAX query in Query Designer of Report Builder in SSRS (KB4503386)	Analysis Services	Analysis Services	Windows
12823369	FIX: DAX query requires more than 200 times of memory than the size of the database in SQL Server 2017 multidimensional model database (KB4503385)	Analysis Services	Analysis Services	Windows
12710985	FIX: CDC Source preview fails with “The given key was not present in the dictionary” error in SQL Server 2017 (KB4500595)	Integration Services	CDC	Windows
(…and many more - see the full JSON data for the complete list!)

Downloading CU15¶

For Windows (Recommended): Head over to the Microsoft Download Center: Download CU15. If you hit a snag, contact Microsoft Customer Service and Support.

For Windows (Microsoft Update Catalog): You can also grab this and future CUs from the Microsoft Update Catalog. But hey, always go for the latest CU if you can. Download CU15 (Catalog)

For Linux: First, make sure you have the Cumulative Update repository configured. Then, use your platform’s update command. Full instructions and download links are in the SQL Server 2017 Release Notes.

File Information: Verifying Your Download¶

Double-check your downloaded SQLServer2017-KB4498951-x64.exe file by calculating its SHA256 hash using:

certutil -hashfile SQLServer2017-KB4498951-x64.exe SHA256

The hash should be: F10ABC85A6681E0FFCA40296159B97A6C1BEC81435D5F282337C8D755433C68E

Detailed file information, including versions, sizes, and timestamps for various components, is available in the original JSON data.

Prerequisites and Restart Information¶

You’ll need SQL Server 2017 running to install this CU. A restart might be necessary after installation.

Important Notices: Pacemaker and Query Store¶

• Pacemaker: A change in behavior with the start-failure-is-fatal setting in distributions using Pacemaker 1.1.18-11.el7 is addressed. Workarounds are detailed in the original text.
• Query Store: If you’re using Query Store and upgrading from CU2 directly to CU3 or later, run the provided SQL script (available in the original JSON data).

Hybrid Environments¶

Deploying to a hybrid setup? Review the information in the original JSON concerning Always On, replication, cluster, and mirroring before you proceed.

Component Updates and Support¶

This CU covers updates for all SQL Server 2017 components. It only updates the components currently installed. If you add a feature (like Analysis Services) after applying CU15, you’ll need to reapply the CU.

Need more help? Don’t hesitate to create a service request with Microsoft Support.

We hope this rundown of SQL Server 2017 CU15 was helpful. Got thoughts, questions, or cool stories about your SQL Server adventures? Share them in the comments below! Stay tuned for more SQL Server updates, and we’ll catch you in the next one!