Note
Access to this page requires authorization. You can try signing in or .
Access to this page requires authorization. You can try .
KB5008996 - Cumulative Update 15 for SQL Server 2019
Release Date: January 27, 2022
Version: 15.0.4198.2
Summary
This article describes Cumulative Update package 15 (CU15) for Microsoft SQL Server 2019. This update contains 36 fixes that were issued after the release of SQL Server 2019 Cumulative Update 14, and it updates components in the following builds:
- SQL Server - Product version: 15.0.4198.2, file version: 2019.150.4198.2
- Analysis Services - Product version: 15.0.35.22, file version: 2018.150.35.22
Known issues in this update
Incorrect behavior of SESSION_CONTEXT in parallel plans
Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.
For more information, see the Known issues section in SESSION_CONTEXT.
Improvements and fixes included in this cumulative 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 "#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 | Description | Fix area | Component | Platform |
|---|---|---|---|---|
| 14448989 | Fixes an issue where AVERAGEX(CURRENTGROUP()) function returns the incorrect result that is close to 0 unless you add 0.0 to the measure in the DAX query. |
Analysis Services | Analysis Services | Windows |
| 14126931 | Fixes an issue where the tooltip of column name doesn't display in SQL Server 2019 Master Data Services (MDS). | Master Data Services | Client | Windows |
| 14393059 | Fixes an issue about inconsistent data if you add a date that is between last day of 1899 and first day of March 1900 in the MDS add-in for Excel in SQL Server 2019. | Master Data Services | Master Data Services | Windows |
| 14253634 | Fixes an issue where Distributed Replay Client may fail with an unhandled exception. This fix is for the Distributed Replay Client that is released with SQL Server 2019. The following is the error you may observe in the output/log file: <DateTime> OPERATIONAL [Common] Unhandled exception is encountered. [Exception Code = 3221225477] <DateTime> OPERATIONAL [Common] Invoking dump. <DateTime> OPERATIONAL [Common] Service terminating. |
SQL Server Client Tools | Database Performance Tools | Windows |
| 14428866 | Fixes an issue where the Shrink Database task in maintenance plans doesn't work in SQL Server 2019. | SQL Server Client Tools | SSMS | Windows |
| 14043526 | FIX: Buffer overruns when data buffer spans multiple SNI packets (KB5010234) | SQL Server Connectivity | Protocols | Windows |
| 14500584 | FIX: Database corruption after creating an external library in SQL Server 2019 (KB5010653) | SQL Server Engine | Extensibility | All |
| 14401565 | Fixes an access violation that occurs when you use FileTable in SQL Server 2019. | SQL Server Engine | FileStream and FileTable | Windows |
| 14364622 | Fixes an issue where assertion failure on secondary replica when you use Always On availability groups in high-latency networks in SQL Server 2019. You may see this assert failure in the error log: Assertion: File: <"e:\\b\\s3\\sources\\sql\\ntdbms\\storeng\\dfs\\trans\\lsnlocmap.cpp">, line=358 Failed Assertion = 'pos - pndx < map->EntryCount' |
SQL Server Engine | High Availability and Disaster Recovery | Windows |
| 14396483 | Adds improvement to capture sp_server_diagnostics XEvent in an AlwaysOn_health XEvent session when STATE is 3 (ERROR) to diagnose HADR Health Events. |
SQL Server Engine | High Availability and Disaster Recovery | Windows |
| 14396775 | Adds the Reverting progress to SQL Server error logs in SQL Server 2019 just like the Recovery progress. | SQL Server Engine | High Availability and Disaster Recovery | Windows |
| 14401590 | Fixes an error that occurs after a failover of a Distributed Availability Group that attempts to connect to the secondary AG listener with application intent set to READ ONLY. |
SQL Server Engine | High Availability and Disaster Recovery | Windows |
| 14300646 | Fixes the following insufficient memory error that occurs during In-Memory Online Transactional Processing (OLTP) if application native procedures update tables that have Large Object (LOB) columns and don't specify the LOB column in the UPDATE list: <DateTime> Disallowing page allocations for database 'Retail' due to insufficient memory in the resource pool 'IMOLTP'. <DateTime> XTP failed page allocation due to memory pressure: FAIL_PAGE_ALLOCATION 8 |
SQL Server Engine | In-Memory OLTP | All |
| 13313683 | Improvement: Add 1 (true) and 0 (false) as valid values to mssql-conf Boolean settings (KB5010246) | SQL Server Engine | Linux | Linux |
| 14196082 | Improvement: Add mssql-conf and adutil utilities to SQL Server 2019 (KB5008647) | SQL Server Engine | Linux | Linux |
| 14288034 | Adds an improvement to enhance the security of machine keys by enabling you to change the default machine key location to a custom location by using SQL Platform Abstraction Layer (PAL) encryption settings. | SQL Server Engine | Linux | Linux |
| 14401082 | Fixes a committed memory accounting issue, which under some circumstances, FAIL_PAGE_ALLOCATION error could occur a few days after starting SQL Server services on Linux. |
SQL Server Engine | Linux | Linux |
| 14465885 | Fixes the following error that occurs when you back up a database by using virtual device interface (VDI) on ubuntu docker container installed SQL Server 2019: Host_<DeviceName>_SQLVDIMemoryName_0: ClientBufferAreaManager::SyncWithGlobalTable: Open(hBufferMemory): error 2Host_<DeviceName>_SQLVDIMemoryName_0: TriggerAbort: invoked: error 0Host_<DeviceName>_SQLVDIMemoryName_0: TriggerAbort: ChannelSem: error 2Features returned by SQL Server: 0x10000 Opening the device. VDS::OpenDevice fails: x80770004 Msg 18210, Level 16, State 1, Server <ServerName>, Line <LineNumber> BackupVirtualDeviceSet::AllocateBuffer: failure on backup device '<DeviceName>'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.). Msg 3013, Level 16, State 1, Server <ServerName>, Line <LineNumber> BACKUP DATABASE is terminating abnormally. |
SQL Server Engine | Linux | Linux |
| 14289674 | Fixes an issue where a filtered index becomes corrupted after you drop a computed column on the same table, and the filtered index corruptions are reported as 8951 and 8955 errors when you run DBCC CHECKTABLE WITH EXTENDED_LOGICAL_CHECKS. |
SQL Server Engine | Metadata | Windows |
| 14320308 | Fixes the memory release issue in execution of the STDistance spatial method while using spatial index. Before the fix, memory usage of MEMORYCLERK_SOSNODE gradually grew until all the memory available is taken. Note: This fix requires that trace flag 8119 be in effect. You can enable the flag through DBCC TRACEON. However, we recommend that you apply it as a startup parameter so that it isn't removed when SQL Server restarts. |
SQL Server Engine | Metadata | Windows |
| 14382474 | Fixes an issue where the output of sp_pkeys KEY_SEQ column doesn't conform to the ordering of columns defined in the Primary Key. |
SQL Server Engine | Metadata | Windows |
| 14382100 | Fixes an issue where the dm_db_page_info function may record spurious corrupted pages entries in the suspect_pages table when calling the function against the transaction log file. |
SQL Server Engine | Methods to access stored data | Windows |
| 14312688 | Fixes an issue where java.nio.BufferOverflowException error occurs when using PolyBase external tables to query data from Hadoop. Note: This error occurs when querying from a file that has columns of type varchar or nvarchar with a width greater than 256 characters. |
SQL Server Engine | PolyBase | All |
| 14419546 | FIX: Physical reads are counted twice for read-ahead (KB5009753) | SQL Server Engine | Query Execution | All |
| 14488550 | Fixes a parallel query executing in batch mode that may cause an access violation and memory dump after installing CU14. | SQL Server Engine | Query Execution | Windows |
| 14491100 | Fixes an access violation that occurs in CXPort::Close after you use SQL Server 2019 Cumulative Update 14 (CU14). |
SQL Server Engine | Query Execution | Windows |
| 14394202 | Fixes the following error 104 that occurs when you use scalar User-Defined Function (UDF) lnlining in the ORDER BY clause during the query compilation that has a UNION operator: Msg 104, Level 16, State 1, Line <LineNumber> ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator. |
SQL Server Engine | Query Optimizer | All |
| 14416748 | Fixes an assertion in CQPOnDemandTask::ExecuteQPJob if auto async update statistics is enabled. You may see this assert failure in the error log: Assertion: File: <sosmemobj.cpp>, line=2774 Failed Assertion = 'pvb->FLargeAlloc () == FALSE' |
SQL Server Engine | Query Optimizer | Windows |
| 14434937 | Fixes an issue where the specific statement for compilation in stored procedures seems "stuck" and shows sqlsource_transform until manual intervention. |
SQL Server Engine | Query Optimizer | Windows |
| 14165626 | Fixes an issue where different conversion results are displayed in publisher and subscriber database tables when using the ASCII function to convert a column. For more information, see ASCII function returns different results in Publisher and Subscriber database tables. | SQL Server Engine | Replication | Windows |
| 14227331 | Fixes an issue where the default trace on Linux rolls over before the limit size of 20 MB. | SQL Server Engine | SQL OS | Linux |
| 14412969 | Fixes the access violation sqldk!StringVPrintfWorkerW that occurs during the compilation of the query for Dynamic Management Views (DMVs) sys.dm_os_ring_buffers. |
SQL Server Engine | SQL OS | Windows |
| 14421838 | Fixes a system-wide low memory issue that occurs when SQL Server commits memory above the maximum server memory under the memory model with the Lock Pages In Memory. Note: You should install startup trace flag 8121 to enable this fix. |
SQL Server Engine | SQL OS | Windows |
| 14497737 | Adds improvement in capturing memory dumps on unexpected crashes in SQL Server 2019 on Linux. | SQL Server Engine | SQL OS | Linux |
| 14459544 | Improvement: Add the usage of signed certificates with multiple DNS names (KB5010555) | SQL Server Engine | Surface Area | All |
| 14332270 | Fixes an issue where Cumulative Update (CU) patching fails with the following message when you set default data directory to Azure Blob Storage URL: The given path's format is not supported. Exception Type "System.NotSupportedException" Note: To work around the issue, you can change the data default directory to a local directory and rerun the SQL patch. |
SQL Setup | Patching | Windows |
How to obtain or download this or the latest cumulative update package
File information
Notes for this update
How to uninstall this update
References
- Announcing updates to the SQL Server Incremental Servicing Model (ISM)
- SQL Server Service Packs are no longer supported starting from SQL Server 2017
- Determine which version and edition of SQL Server Database Engine is running
- Servicing models for SQL Server
- 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
Feedback
Was this page helpful?