Cumulative Update 9 for SQL Server 2017

Applies to: SQL Server 2017 on Windows (all editions)SQL Server 2017 on Linux (all editions)

This article describes Cumulative Update package 9 (CU9) (build number: 14.0.3030.27) for SQL Server 2017. This update contains fixes that were released after the initial release of SQL Server 2017.

This article also provides important information about the following situations:

Cumulative update

Cumulative updates (CU) are now available at the Microsoft Download Center.

Only the most recent CU that was released for SQL Server 2017 is available at the Download Center.

CU packages for Linux are available at https://packages.microsoft.com/.

Notes

  • Each new CU contains all the fixes that were included with the previous CU for the installed version of SQL Server.
  • SQL Server CUs are certified to the same levels as Service Packs, and should be installed at the same level of confidence.
  • Microsoft recommends ongoing, proactive installation of CUs as they become available according to these guidelines:
     
    • 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.
  • We recommend that you test CUs before you deploy them to production environments.
 

How to obtain this cumulative update package for Windows


The following update is available from the Microsoft Download Center:
 
If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.

Note After future cumulative updates are released for SQL Server 2017, this and all previous CUs can be located and downloaded from the Microsoft Update Catalog. However, we recommend that you always install the latest cumulative update available.

How to obtain this cumulative update package for Linux


To update Linux to the latest CU, you must first have the Cumulative Update repository configured. Then, update your SQL Server packages by using the appropriate platform-specific update command.

For installation instructions and direct links to the CU package downloads, see the Release notes.

Additional hotfixes that are included in this cumulative update package


VSTS bug number KB article number Description Fix area Platform
12144190 4340069 FIX: SQL Server 2017 on Linux shuts down unexpectedly during the recovery of an In-Memory OLTP database In-Memory OLTP Linux
12041154 4340134 FIX: Error when a role that is defined with a restricted column is used to run a drillthrough query in SSAS Analysis Services Windows
12128861 4340747 FIX: SQLDUMPER.EXE initiated dumps may take a long time to complete dump generation process for SQL Server 2017 on Linux SQL Engine Linux
12168709 4010460 FIX: A .NET Framework error occurred when you update the reference table of a Fuzzy Lookup transformation in SSIS Integration Services Windows
12138685 4339613 FIX: “Unclosed quotation mark after the character string” error occurs on the MDS explorer when you try to add a new member to an entity in SQL Server Data Quality Services (DQS) Windows
12107546 4338890 FIX: An instance of SQL Server may appear unresponsive then a "Non-yielding Scheduler" error may occur in SQL Server 2016 SQL Engine Windows
11922902 4316858 FIX: "Corrupted index" message and server disconnection when an update statistics query uses hash aggregate on SQL Server SQL performance All
12149855 4341219 FIX: A split brain scenario occurs after a failover when using AlwaysOn availability groups with external cluster technology in SQL Server 2017 High Availability All
12111717 4340837 FIX: Error 3906 when a hotfix is applied on a SQL Server that has a database snapshot on a pull subscription database SQL Engine Windows
11983925 4133164 FIX: Error when a SQL Server Agent job runs a PowerShell command to enumerate permissions of the database Management Tools Windows
12121216 4339664 FIX: Exception error occurs when you try to refresh data for a pivot table in Excel in SSAS 2017 Analysis Services Windows
12123248 4340742 FIX: Access to SSAS by using HTTP fails in SQL Server Analysis Services Windows
12162067 4341264 Improvement: Allow SQL Server Agent jobs to start without waiting for all databases to get recovered in SQL Server 2017 on Linux SQL Engine Linux
12186129 4101502 FIX: TDE enabled database backup with compression causes database corruption in SQL Server SQL Engine All
12129434 4134601 FIX: “Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClientUI” error when a “Process Full” operation is run in SQL Server Analysis Services Windows
12162425 4341221 FIX: VSS backup fails in secondary replica of Basic Availability Groups in SQL Server 2016 and 2017 SQL Engine Windows
12108225 4339858 FIX: Parallel redo does not work after you disable Trace Flag 3459 in an instance of SQL Server High Availability All
12061383 4341253 FIX: DMVs sys.dm_db_log_stats and sys.dm_db_log_info may return incorrect values for the last database of the SQL Server 2016 instance SQL Engine Windows

Notes for this update


Hybrid environments deployment

When you deploy an update to a hybrid environment (such as AlwaysOn, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:
 

Cumulative update package information


Prerequisites

To apply this cumulative update package, you must be running SQL Server 2017.
 

Restart information

You may have to restart the computer after you apply this cumulative update package.
 

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Pacemaker notice


IMPORTANT

All distributions (including RHEL 7.3 and 7.4) that use the latest available Pacemaker package 1.1.18-11.el7 introduce a behavior change for the start-failure-is-fatal cluster setting when its value is false. This change affects the failover workflow. If a primary replica experiences an outage, the cluster is expected to failover to one of the available secondary replicas. Instead, users will notice that the cluster keeps trying to start the failed primary replica. If that primary never comes online (because of a permanent outage), the cluster never fails over to another available secondary replica.

This issue affects all SQL Server versions, regardless of the cumulative update version that they are on.

To mitigate the issue, use either of the following methods.

Method 1

Follow these steps:

  1. Remove the start-failure-is-fatal override from the existing cluster. 
       # RHEL, Ubuntu         pcs property unset start-failure-is-fatal         # or         pcs property set start-failure-is-fatal=true   # SLES         crm configure property start-failure-is-fatal=true
  2. Decrease the cluster-recheck-interval value. 
       # RHEL, Ubuntu         pcs property set cluster-recheck-interval=<Xmin>   # SLES         crm configure property cluster-recheck-interval=<Xmin>
  3. Add the failure-timeout meta property to each AG resource. 
       # RHEL, Ubuntu         pcs resource update ag1 meta failure-timeout=60s   # SLES         crm configure edit ag1      # In the text editor, add `meta failure-timeout=60s` after any `param`s and before any `op`s
     

    Note In this code, substitute the value for <Xmin> as appropriate. If a replica goes down, the cluster tries to restart the replica at an interval that is bound by the failure-timeout value and the cluster-recheck-interval value. For example, if failure-timeout is set to 60 seconds and cluster-recheck-interval is set to 120 seconds, the restart is tried at an interval that is greater than 60 seconds but less than 120 seconds. We recommend that you set failure-timeout to 60s and cluster-recheck-interval to a value that is greater than 60 seconds. Setting cluster-recheck-interval to a small value is not recommended. For more information, refer to the Pacemaker documentation or consult the system provider.


Method 2

Revert to Pacemaker version 1.1.16.

    Query Store notice


    IMPORTANT

    If you use the Query Store feature, and you have previously installed Cumulative Update 2 (CU2) (14.0.3008.27), the following requirement applies to you:

    After you install Cumulative Update 3 (CU3) (14.0.3015.40) or a later CU, you must immediately run the following script to delete all plans that were collected by Query Store while CU2 was installed:

    SET NOCOUNT ON;DROP TABLE IF EXISTS #tmpUserDBs;SELECT [database_id], 0 AS [IsDone]INTO #tmpUserDBsFROM master.sys.databasesWHERE [database_id] > 4 AND [state] = 0 -- must be ONLINE AND is_read_only = 0 -- cannot be READ_ONLY AND [database_id] NOT IN (SELECT dr.database_id FROM sys.dm_hadr_database_replica_states dr -- Except all local Always On secondary replicas  INNER JOIN sys.dm_hadr_availability_replica_states rs ON dr.group_id = rs.group_id  INNER JOIN sys.databases d ON dr.database_id = d.database_id  WHERE rs.role = 2 -- Is Secondary   AND dr.is_local = 1   AND rs.is_local = 1)DECLARE @userDB sysname;WHILE (SELECT COUNT([database_id]) FROM #tmpUserDBs WHERE [IsDone] = 0) > 0BEGIN SELECT TOP 1 @userDB = DB_NAME([database_id]) FROM #tmpUserDBs WHERE [IsDone] = 0 -- PRINT 'Working on database ' + @userDB EXEC ('USE [' + @userDB + '];DECLARE @clearPlan bigint, @clearQry bigint;IF EXISTS (SELECT [actual_state] FROM sys.database_query_store_options WHERE [actual_state] IN (1,2))BEGIN IF EXISTS (SELECT plan_id FROM sys.query_store_plan WHERE engine_version = ''14.0.3008.27'') BEGIN  DROP TABLE IF EXISTS #tmpclearPlans;  SELECT plan_id, query_id, 0 AS [IsDone]  INTO #tmpclearPlans  FROM sys.query_store_plan WHERE engine_version = ''14.0.3008.27''  WHILE (SELECT COUNT(plan_id) FROM #tmpclearPlans WHERE [IsDone] = 0) > 0  BEGIN   SELECT TOP 1 @clearPlan = plan_id, @clearQry = query_id FROM #tmpclearPlans WHERE [IsDone] = 0   EXECUTE sys.sp_query_store_unforce_plan @clearQry, @clearPlan;   EXECUTE sys.sp_query_store_remove_plan @clearPlan;   UPDATE #tmpclearPlans   SET [IsDone] = 1   WHERE plan_id = @clearPlan AND query_id = @clearQry  END;  PRINT ''- Cleared possibly affected plans in database [' + @userDB + ']'' END ELSE BEGIN  PRINT ''- No affected plans in database [' + @userDB + ']'' ENDENDELSEBEGIN PRINT ''- Query Store not enabled in database [' + @userDB + ']''END')  UPDATE #tmpUserDBs  SET [IsDone] = 1  WHERE [database_id] = DB_ID(@userDB)END