KB5016394 - Cumulative Update 17 for SQL Server 2019
Leidimo data:
2022-08-11
Versija:
15.0.4249.2
Summary
This article describes Cumulative Update package 17 (CU17) for Microsoft SQL Server 2019. This update contains 38 fixes that were issued after the release of SQL Server 2019 Cumulative Update 16, and it updates components in the following builds:
-
SQL Server - Product version: 15.0.4249.2, file version: 2019.150.4249.2
-
Analysis Services - Product version: 15.0.35.33, file version: 2018.150.35.33
Known issues in this update
SQL Server 2019 CU14 introduced a fix to address wrong results in parallel plans returned by built-in SESSION_CONTEXT. However, this fix could cause Access Violation dump files while resetting the SESSION for reuse. To mitigate this issue, you can disable the original fix, and disable the parallelism for built-in SESSION_CONTEXT to avoid wrong results. To do this, use the following trace flags:
-
11042 - This trace flag disables the parallelism for built-in SESSION_CONTEXT.
-
9432 - This trace flag disables the fix introduced in SQL Server 2019 CU14.
Microsoft is working on a fix for this issue that will be available in a future CU.
Improvements and fixes included in this update
A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2019 and SQL Server 2017. Select to download this Excel file now.
Note: Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#bkmk_NNNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.
For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following Microsoft Knowledge Base articles.
|
Bug reference |
KB article number |
Description |
Fix area |
Platform |
||
|---|---|---|---|---|---|---|
|
Adds support for the missing "Implementation" parameter when you use the SharePoint Online Lists. |
Analysis Services |
Windows |
||||
|
Resolves the Denial of Service (DoS) vulnerability for the Newtonsoft library in SQL Server 2019. |
Analysis Services |
Windows |
||||
|
5016729 |
Improvement: Enable distributed availability groups on SQL Server Standard editions |
High Availability |
All |
|||
|
The dynamic management view (DMV) sys.dm_hadr_availability_replica_cluster_nodes returns the invalid node_name for certain queries after applying SQL Server 2019 Cumulative Update 14 (CU14). |
High Availability |
Windows |
||||
|
A database may fail to resume synchronization during the failover of an Always On availability group because the session working on the database synchronization or recovery is killed by another session. |
High Availability |
All |
||||
|
An assertion dump occurs in sqlmin!BOSLockThreadHashTable::AddEntry during a log backup on a secondary replica of an availability group. |
High Availability |
All |
||||
|
A latch time-out occurs and the IOCP listener stalls when Service Broker connects to an endpoint by using database mirroring. Note This fix is available when TF 12323 is enabled. |
High Availability |
Windows |
||||
|
The read-only request still goes to the read-write primary node in an Always On availability group when the read-only routing list node goes down. |
High Availability |
All |
||||
|
A memory leak occurs under "Range Index Heap" on the in-memory table that has non-clustered indexes, whenever there are concurrent inserts. |
In-Memory OLTP |
All |
||||
|
A memory leak occurs in the range index of in-memory tables after the parallel index scan. |
In-Memory OLTP |
All |
||||
|
An error occurs when you execute the internal.cleanup_server_log stored procedure in the SSISDB database. Here is the error message: #MS_SSISServerCleanupJobLogin##. A cursor with the name 'execution_cursor' does not exist. [SQLSTATE 34000] (Error 16916) |
Integration Services |
Windows |
||||
|
5016780 |
SQL Server Engine |
All |
||||
|
5013181 |
FIX: A subscription is still active after the distribution retention period expires |
SQL Server Engine |
Windows |
|||
|
5017009 |
FIX: sp_replmonitorsubscriptionpendingcmds returns incorrect pending commands for P2P replication |
SQL Server Engine |
Windows |
|||
|
When you use the AZDATA BDC ROTATE command to rotate the password of a SQL Server big data cluster that uses Active Directory, you receive the following error message: |
SQL Server Engine |
Linux |
||||
|
Improves the response time of the system view sys.spt_columns_odbc_view on Linux. |
SQL Server Engine |
Linux |
||||
|
The optimizer may fail to produce the plan and throw an error when you enable the Scalar User-Defined Function (UDF) Inlining feature and try to update a partitioned view by using the output of the UDF. Here is the error message: Msg 8624, Level 16, State 21, Line <LineNumber> Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. |
SQL Server Engine |
Windows |
||||
|
Error 9003 occurs with the incorrect log sequence number (LSN) when you do a subsequent restore after specifying the LSN at the virtual log file (VLF) boundary by using the RESTORE WITH STANDBY statement. Here is the error message: Msg 3013, Level 16, State 1, Line <LineNumber> RESTORE DATABASE is terminating abnormally. Msg 9003, Level 17, State 11, Line <LineNumber> The log scan number (<LogScanNumber>) passed to log scan in database '<DatabaseName>' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. |
SQL Server Engine |
Windows |
||||
|
This fix resolves the following issues:
|
SQL Server Engine |
All |
||||
|
Traversing long IAM chains may cause a non-yielding scheduler and associated dump. |
SQL Server Engine |
All |
||||
|
QDS remains stuck in read-only mode if the size-based cleanup index rebuild releases space asynchronously. |
SQL Server Engine |
Windows |
||||
|
An instance of SQL Server Express LocalDB fails to start and returns error 9003 after multiple backups on the model database. |
SQL Server Engine |
Windows |
||||
|
An access violation occurs in CSession::DeleteBlobHandleFactoryPool while resetting the SESSION for reuse. |
SQL Server Engine |
Windows |
||||
|
Incorrect reporting of physical sector size for Linux block devices can cause unexpected "misaligned log IOs" warnings for log shipping and Always On availability groups. |
SQL Server Engine |
Linux |
||||
|
The last-chance exception handling for a Columnstore index occurs after a log-full 9002 error. |
SQL Server Engine |
All |
||||
|
An access violation occurs when XVBChainTails::UpdateChainTails updates m_pNewVersionChainTailInsert and m_pOldVersionChainTailInsert and these values are not allocated. |
SQL Server Engine |
All |
||||
|
An access violation occurs when you create a CLR assembly after restoring a database from a snapshot. |
SQL Server Engine |
Windows |
||||
|
When you create a peer-to-peer publication by using the last-write-wins conflict resolution policy, and one or few articles in this publication have just 1 column which is the primary key column, running the distribution agent fails and returns the following error message: Incorrect syntax near '$sys_mw_cd_id'. |
SQL Server Engine |
Windows |
||||
|
The floating-point exception error 3628 occurs when you run a full-text query that contains a FREETEXTTABLE function. |
SQL Server Engine |
All |
||||
|
5017100 |
FIX: Access violation dump file occurs during a columnstore index scan |
SQL performance |
All |
|||
|
Error 2706 occurs when you run DBCC CHECKDB WITH EXTENDED_LOGICAL_CHECKS against a database by using the Table-Valued Function (TVF) that uses indexes. Here is the error message: Table '%.*ls' does not exist. |
SQL performance |
Windows |
||||
|
Creating edge constraints on graph tables meets an access violation when you use a node table instead of an edge table in the constraint. |
SQL performance |
All |
||||
|
An access violation occurs, and the query is terminated when you use sp_cursoropen for SHORTEST_PATH over graph tables. |
SQL performance |
All |
||||
|
An access violation occurs when you try to use an aggregate function together with WITHIN GROUP (GRAPH PATH), and the query doesn't have a suitable MATCH clause. |
SQL performance |
All |
||||
|
An access violation or an assertion failure occurs when you use the LAST_QUERY_PLAN_STATS feature while running a parallel query. |
SQL performance |
Windows |
||||
|
In Microsoft SQL Server 2019, an index creation script fails and returns error message 8624. Here is the error message: Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. |
SQL performance |
Windows |
||||
|
A system assertion failure occurs and the query is terminated when you try to use a derived table within a MATCH predicate. |
SQL performance |
All |
||||
|
In Microsoft SQL Server 2019, running parameterized queries skips the SelOnSeqPrj rule. Therefore, pushdown does not occur. |
SQL performance |
All |
||||
|
An assertion dump occurs in RaiseInternalError while processing binary large object (BLOB) data. |
SQL performance |
Windows |
How to obtain or download this or the latest cumulative update package
The following update is available from the Microsoft Download Center:
Download the latest cumulative update package for SQL Server 2019 now
Notes:
-
Microsoft Download Center will always present the latest SQL Server 2019 CU release.
-
If the download page does not appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.
The following update is available from the Microsoft Update Catalog:
Download the cumulative update package for SQL Server 2019 CU17 now
Notes:
-
Microsoft Update Catalog contains this SQL Server 2019 CU and previously released SQL Server 2019 CU releases.
-
This CU is also available through Windows Server Update Services (WSUS).
-
We recommend that you always install the latest cumulative update that is available.
To update SQL Server 2019 on 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 SQL Server 2019 Release Notes.
To upgrade Microsoft SQL Server 2019 Big Data Clusters (BDC) on Linux to the latest CU, see the Big Data Clusters Deployment Guidance.
Starting in SQL Server 2019 CU1, you can perform in-place upgrades for Big Data Clusters from the production supported releases (SQL Server 2019 GDR1). For more information, see How to upgrade SQL Server Big Data Clusters.
For additional information, see the Big Data Clusters release notes.
File information
You can verify the download by computing the hash of the SQLServer2019-KB5016394-x64.exe file through the following command:
-
certutil -hashfile SQLServer2019-KB5016394-x64.exe SHA256
|
File name |
SHA256 hash |
|---|---|
|
SQLServer2019-KB5016394-x64.exe |
B3AF212A50B79CA5B780D0EEB895572C6567ECD516135C0D221309CDF637C8AB |
The English version of this package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|
x64-based versions SQL Server 2019 Analysis Service
|
Notes for this update
To apply this cumulative update package, you must be running SQL Server 2019.
You might have to restart the computer after you apply this cumulative update package.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
This article also provides the following important information:
Analysis Services CU build version
Beginning in Microsoft SQL Server 2017, the Analysis Services build version number and SQL Server Database Engine build version number do not match. For more information, see Verify Analysis Services cumulative update build version.
Cumulative updates (CU)
-
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.
-
We recommend 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 SQL Server CUs before you deploy them to production environments.
When you deploy an update to a hybrid environment (such as Always On, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:
-
SQL Server failover cluster rolling update and service pack process
Notes: If you do not want to use the rolling update process, follow these steps to apply an update:
-
Install the update on the passive node.
-
Install the update on the active node (requires a service restart).
-
-
Upgrade and update of availability group servers that use minimal downtime and data loss
Note: If you enabled Always On together with SSISDB catalog, see the information about SSIS with Always On for more information about how to apply an update in these environments.
-
How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology
-
How to apply a hotfix for SQL Server in a replication topology
SQL Server CUs are currently multilingual. Therefore, this CU package is not specific to one language. It applies to all supported languages.
One CU package includes all available updates for all SQL Server 2019 components (features). However, the cumulative update package updates only those components that are currently installed on the SQL Server instance that you select to be serviced. If a SQL Server feature (for example, Analysis Services) is added to the instance after this CU is applied, you must re-apply this CU to update the new feature to this CU.
If additional issues occur, or if any troubleshooting is required, you might have to create a service request. The usual support costs will apply to additional support questions and to issues that do not qualify for this specific cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers, or to create a separate service request, go to the Microsoft support website.
How to uninstall this update
-
In Control Panel, open the Programs and Features item, and then select View installed updates.
-
Locate the entry that corresponds to this cumulative update package under SQL Server 2019.
-
Press and hold (or right-click) the entry, and then select Uninstall.
To uninstall this CU on Linux, you must roll back the package to the previous version. For more information about how to roll back the installation, see Rollback SQL Server.
References
-
Announcing updates to the SQL Server Incremental Servicing Model (ISM)
-
SQL Server Service Packs are discontinued starting from SQL Server 2017
-
Determining which version and edition of SQL Server Database Engine is running
-
Naming schema and Fix area descriptions for SQL Server software update packages
-
Description of the standard terminology that is used to describe Microsoft software updates
