There is a known issue that affects using database snapshots in SQL Server 2019 CU7. Note that using DBCC CHECKDB is also affected because this generates a database snapshot. This issue is fixed in SQL Server 2019 CU8. To get this fix, apply SQL Server 2019 CU8 or any later SQL Server 2019 CU release.
If you downloaded the CU7 package file before September 23, 2020, we recommend that you do not install it. Please move to SQL Server CU8 or a later CU release.
If you have already applied SQL Server 2019 CU7, please uninstall it and move to SQL Server CU8 or a later CU release.
If you have already applied SQL Server 2019 CU7, and you created a database snapshot, plan to drop the database snapshot, and then apply SQL Server 2019 CU8 or a later CU release before you re-create your database snapshot.
More details will be made available in the SQL Release Blog.
This article describes Cumulative Update package 7 (CU7) for Microsoft 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 Microsoft Knowledge Base articles.
|Bug Reference||KB article number||Description||Fix area||Platform|
|13598931||4561305||FIX: Concurrent inserts against tables with columnstore indexes may cause queries to hang in SQL Server 2016 and 2019||All|
|13606684||When you run a SELECT query in Read Committed Snapshot Isolation (RCSI) on Clustered Columnstore Index (CCI) on a table in SQL Server 2019, the query may return incorrect number of rows under rare conditions.||SQL Engine||All|
|13607141||Fixes an assertion exception that occurs when you query the DMV sys.dm_hadr_automatic_seeding.||High Availability||All|
|13607158||This update fixes an issue with sys.dm_db_stats_histogram not showing NULL value histogram step.||SQL performance||All|
|13621665||4574801||FIX: Incorrect results occur when you run PolyBase query to read text files from Hadoop in SQL Server 2019||SQL Engine||All|
|13635355||4578395||FIX: Error occurs when using DBCC operations while TDE key change happens in SQL Server 2019||SQL security||All|
|13636909||4034376||FIX: Couldn't disable "change data capture" if any column is encrypted by "Always Encrypted" feature of SQL Server||SQL Engine||All|
|13643332||4538581||FIX: Scalar UDF Inlining issues in SQL Server 2019||SQL Engine||All|
|13643390||Fixes failure of SQL Server Extensibility Runtimes Setup on FIPS compliant servers.||SQL Engine||All|
|13643805||4577594||FIX: Add language and extension directories to the PATH environment variable in SQL Server 2019||SQL Engine||All|
|13647491||4576778||FIX: Table Variable Deferred Compilation feature on SQL Server 2019 database remains enabled when database compatibility level is 140 or lower||SQL Engine||All|
|13647889||Python and R CAB files for SQL Server Machine Learning Services on Windows and mssql-mlservices packages on Linux are updated to version 188.8.131.528. On Windows, "Cannot resume session with terminated pooled proccess" error is fixed while launching Python/R runtimes. On Linux, this update enables successful installation of mssql-mlservices-mlm-r package on RHEL8.||SQL Engine||All|
|13669080||4577836||FIX: Inconsistency occurs when ghost rows are inserted into mapping index rowset||SQL Engine||All|
|13491695||4578011||FIX: Unable to restore SQL Server database from previous versions on NVMe device partitioned in 4K block size||SQL Engine||Linux|
|13512207||4575453||FIX: SQL Server fails to start when remote admin connections are enabled and IPV6 is disabled on the host||SQL Engine||Linux|
|13578549||Improvement: Enables RLS feature for PolyBase by default in SQL Server 2019.||SQL Engine||Linux|
|13607140||This updates adds detailed error information to the pacemaker log when pacemaker agent fails to connect to SQL Server resource to obtain health status.||High Availability||Linux|
|13607142||4569424||FIX: Intermittent Availability Group failover occurs as AG helper connection times out while connecting to SQL Server||High Availability||Linux|
|13607847||4581882||FIX: Restoring database fails due to backup command timeout in SQL Server 2019.||High Availability||Linux|
|13628489||4577591||FIX: Widerow insert to an external table is not supported when the row width is more than 32K in SQL Server 2019||SQL Engine||Linux|
|13634075||4577590||FIX: Error occurs when row width is less than DMS buffer size of 32K and an incorrect return path is chosen in SQL Server 2019||SQL Engine||Linux|
|13651459||4577837||FIX: Queries may fail when storage pool caching is enabled by default in SQL Server 2019 Big Data Cluster||SQL Engine||Linux|
|13657658||4578292||FIX: Error occurs when you try to deploy CU5 or CU6 for SQL Server 2019 BDC by using azdata client 20.0.0 on RHEL host OS||SQL BDC||Linux|
|13567739||Fixes an issue to reduce parallel redo thread shutdown and startup thread messages in error log on servers with fewer cores and more idle databases.||High Availability||Windows|
|13583547||4577561||FIX: Error occurs when you try to filter the members of an entity for numeric values less than or greater than '0' in MDS 2019||Master Data Services||Windows|
|13585628||Fixes intermittent connection issue with SSIS package executions when expression is used for both connection string and password of a connection manager.||Integration services||Windows|
|13586253||4578110||FIX: Error 8992 occurs when you run DBCC CHECKDB on cloned database in SQL Server 2019||SQL Engine||Windows|
|13598885||DBCC CHECKDB reports corruption on spatial index incorrectly if base table has a column called ID.||SQL Engine||Windows|
|13598896||SSRS 2016 URLs are case-sensitive after applying Security update GDRs: KB4532097 and KB4535706.||SQL Engine||Windows|
|13598899||When you concurrently create sub directories in a FileTable directory, a deadlock may occur internally in the SQL Server Engine and all subsequent requests to FileTable directories and files may not respond.||SQL Engine||Windows|
|13598905||When a replication error such as deadlock occurs, random id is inserted in MSRepl_Errors table while it should be just incremented by 1 from the previous id value. This cumulative update (CU) fixes the issue and the MSRepl_Errors will insert entries with row id incremented by 1 instead of using some random value.||SQL Engine||Windows|
|13598907||When you run an ALTER command WITH ROLLBACK IMMEDIATE, the rollback can trigger before the command is processed, thus rolling back transactions even if the ALTER itself fails due to lack of permissions. This fix makes sure that the rollback is processed only after the ALTER command completes.||SQL Engine||Windows|
|13598909||4511771||FIX: Full-Text search auto crawl stops when AG goes offline in SQL Server||SQL Engine||Windows|
|13598911||4563115||FIX: Upgrade script may fail if you use Always On Failover Cluster Instance as a secondary replica in SQL Server 2016 and 2019||SQL Engine||Windows|
|13598925||When DBCC CHECKTABLE, CHECKFILEGROUP and CHECKDB commands are issued against a database with table that contains columnstore index located on read-only non-primary filegroup, you may receive the following error: |
Msg 8921, Level 16, State 1, Line LineNumber
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
|13598927||4560183||FIX: Distributed transactions may experience long waits with DTC_STATE wait type in SQL Server 2016 and 2019||SQL Engine||Windows|
|13598933||FIX: Assertion error occurs on the mirror server during redo process hitting. Assertion: File: <FilePath\FileName>, line = LineNumber Failed Assertion = 'result == LCK_OK'||High Availability||Windows|
|13598937||Access violation exception occurs when a query that references a non-exsting partition function is executed.||SQL performance||Windows|
|13602806||Fixes the Japanese translation for "State" in SQL Configuration Manager.||SQL Engine||Windows|
|13606017||Unable to change the DateTime/Number attributed to NULL in Master Data Services (MDS).||Data Quality Services (DQS)||Windows|
|13607134||4569425||FIX: Transactional replication publications can support URL type device to initialize subscriptions from backups in Azure Blob Storage in SQL Server 2017||SQL Engine||Windows|
|13607135||4567166||FIX: Assertion failure occurs when you try to insert record into a page in fully logged mode in SQL Server 2017 and 2019||SQL Engine||Windows|
|13607136||Error occurs when mashup is used to import from Active Directory (AD) using the default M query generated from the connection wizard. Key Expression Error: The key didn't match any rows in the table||Analysis services||Windows|
|13607143||DELETE statement returns Foreign Key check constraint error even when REFERENCE table has no matching rows. |
Msg 547, Level 16, State 0, Line LineNumber
The DELETE statement conflicted with the REFERENCE constraint "ConstraintName".
The conflict occurred in database "DatabaseName", table "TableName", column 'ColumnName'.
The statement has been terminated.
|13607144||Fixes long duration for Integration Services Project deployment through powershell by improving search of operation messages in deployment process.||Integration services||Windows|
|13607145||Fixes an error that occurs when a session cube is created on a database and you try to query from that session cube. The following error is received when you query the session cube: Server: The operation has been cancelled because there is not enough memory available for the application. If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing the amount of memory available on the machine.||Analysis services||Windows|
|13607160||Column description disappears after exporting/importing models through MDSModelDeploy for an approval required entity in SQL Server 2019.||Data Quality Services (DQS)||Windows|
|13616383||Fixes a performance issue when a query outputs NULL values following a semi join in SQL Server 2019 for a database with UTF8.||SQL performance||Windows|
|13619478||Updates RSetup with the updated FWLINK version 184.108.40.2067.||SQL Engine||Windows|
|13626378||Fixes an issue in MDS Filtered results where the user is not returned to page 1 and the page count is not updated until returning to page 1.||Data Quality Services (DQS)||Windows|
|13627086||Updates the Zulu JRE version to zulu11.37.18-sa-jre220.127.116.11.||SQL Engine||Windows|
|13632226||Fixes an issue in Master Data Services 2019 where you cannot input multiline content in text attributes.||Data Quality Services (DQS)||Windows|
|13667907||Under (rare) certain circumstances, memory grant re-calculation can cause an access violation.||SQL performance||Windows|
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.
Notes for this update
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
- 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