This article describes Cumulative Update package 3 (CU3) for SQL Server 2019. This update contains fixes that were released after the initial release of SQL Server 2019 and updates the SQL Server and Analysis services components to the following builds.
|Component||Product version||File version|
This article also provides important information about the following situations:
- Analysis Services CU build version: Beginning in 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.
- 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 SQL Server CUs before deploying to production environments.
How to obtain this cumulative update package for SQL Server 2019 on Windows
The following update is available from the Microsoft Download Center:
- Note 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.
- Note 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.
How to obtain this cumulative update package for SQL Server 2019 on Linux
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.
How to obtain this cumulative update package for SQL Server 2019 Big Data Clusters (BDC)
To implement SQL Server 2019 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.
List of improvements and fixes included in this Cumulative Update
For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table:
|Bug Reference||KB article number||Description||Fix area||Platform|
|13209410||SQL Server error log contains additional empty lines while printing In-memory OLTP related messages.||In-memory OLTP||All|
|13321064||4538118||Improvement: Enable hybrid buffer pool read caching in SQL Server 2019||SQL Engine||All|
|13359752||4541132||Improvement: Size and retention policy are increased in default XEvent trace system_health in SQL Server 2019 and 2016||SQL Engine||All|
|13317222||Enable SQL checksum sniffer for Pmm pages in hybrid buffer pool.||SQL Engine||All|
|13357974||Due to a new feature called concurrent PFS update in SQL Server 2019 which is enabled by default, in certain rare corner cases, you may encounter non-yielding threads and latch timeout errors in SQL Server.||SQL Engine||All|
|13395279||Updates the Zulu JRE version to zulu11.37.18-sa-jre11.0.6.||SQL Engine||All|
|13388147||When you run a query against sys.dm_db_stats_histogram, it may fail with access violation when a parallel plan is chosen.||SQL performance||All|
|13357938||4538686||Improvement: Add new Protection key feature work for SQL Server 2019 on Linux||SQL Engine||Linux|
|13404121||4548131||FIX: Fail to access openmpi path when running rx jobs in parallel mode with Revo package in Linux SQL Server 2019||SQL Engine||Linux|
|13411046||4548133||FIX: Data length/size of Unicode nvarchar data type column is not correct for OutputDataSet in sp_execute_external_script query in SQL Server 2019 on Linux||SQL Engine||Linux|
|13383620||This update reduces query execution time for BDC storage pool tables and other Polybase external tables.||SQL Engine||Linux|
|13412437||Updates to SQL Server on Linux (mssql mlservices and extensibility) packages to address following issues: ||SQL Engine||Linux|
|13429278||4550657||FIX: Error occurs when you interact with SQL Server Agent in SQL Server 2019||High Availability||Windows|
|13410674||4547890||FIX: ISDBUpgradeWizard.exe throws error when you try to upgrade SSISDB after restoring from earlier versions in SQL Server 2019||Integration Services||Windows|
|13410658||Allow DTSWizard to support AAD when the selected driver is MSOLEDBSQL.||Integration Services||Windows|
|13324032||4529927||FIX: .NET Framework DbDataAdapter.FillSchema method returns NULL on database with compatibility level 140 in SQL Server 2019 and 2017||SQL Engine||Windows|
|13412450||4539172||FIX: Launchpad services fails to start during failover in SQL Server 2019||SQL Engine||Windows|
|13378659||4540121||FIX: sp_execute_external_script doesn't run when you install SQL Server 2019 with Machine Learning Services and a customized Shared feature directory||SQL Engine||Windows|
|13382004||4548523||FIX: Database creation to Azure blob storage from SQL Server 2019 on Linux may fail with error||SQL Engine||Windows|
|13403957||Updates RSetup with the updated FWLINK version 22.214.171.1243.||SQL Engine||Windows|
|13405530||"The JSON DDL request is missing the database name" error occurs when you delete the database property from the descriptive table under the JSON code in SQL Server 2019||SQL Engine||Windows|
|13350041||When you repeatedly run a stored procedure that uses temporary table with indexes on SQL Server 2019, the client may receive an unexpected error with message "A severe error occurred on the current command" and an access violation exception is recorded on the SQL Server. If the same workload is executed on any previous major version of SQL Server, this issue does not occur.||SQL performance||Windows|
|13360725||When you run a SELECT query returning empty/multiple rows with variable assignment in inline-able scalar UDFs, you may receive wrong results.||SQL performance||Windows|
Notes for this update
Under certain circumstances, there is a known uninstall issue with this SQL Server 2019 CU3. If you uninstall this CU, SQL server doesn’t come online and you find the following SQL Server error log message:
The script level for 'system_xevents_modification.sql' in database 'master' cannot be downgraded from XXXXXXXXX to XXXXXXXXX, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database.
Mitigation is to enable Trace Flag - T902, then SQL server will come online and you are done. You don’t need to uninstall it again. To upgrade to new CU you need to remove this flag first.
SQL Server 2019 CU5 or any later CU release contains the fix.
Hybrid environments deployment
- SQL Server failover cluster rolling update and service pack process
Note 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 AlwaysOn together with SSISDB catalog, see the information about SSIS with AlwaysOn 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
- How to install service packs and hotfixes on an instance of SQL Server that is configured to use database mirroring
- Overview of SQL Server Servicing Installation
To apply this Cumulative Update package, you must be running SQL Server 2019.
You may 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.
- 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
- An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
- 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