SQL Server 2022 Updates & Release Notes

This article describes Cumulative Update package 25 (CU25) for Microsoft SQL Server 2022. This update contains 11 fixes that were issued after the release of SQL Server 2022 Cumulative Update 24. It updates components in the following builds:

• SQL Server - Product version: 16.0.4255.1, file version: 2022.160.4255.1
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

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 update

A downloadable Microsoft 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 2022, SQL Server 2019, and SQL Server 2017. 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 "#NNNNNNN" 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 table.

Bug reference - Description - Fix area - Component - Platform

• 4954485 - Fixes an issue in Contained Availability Groups in which DatabaseMail sends email messages without attachments. - SQL Server Client Tools - Database Mail - All
• 4999187 - Fixes an issue in which permissions on stored procedures and other objects in msdb are lost during the SQL Server upgrade process. This issue causes users to lose granted permissions. - SQL Server Engine - Management Services - Windows
• 5028794 - Fixes an access violation error that occurs when querying sys.dm_xe_session_targets on SQL Server instances that are running on Windows Server 2025. - SQL Server Engine - SQL OS - Windows
• 5033534 - Fixes an issue in Contained Availability Group connections in which T-SQL allows only adding a database to the currently connected Contained Availability Group, and also causes additional restrictions for DBCreator roles. - SQL Server Engine - High Availability and Disaster Recovery - All
• 5034739 - Fixes a memory leak issue in which parallel execution of SHORTEST_PATH queries in Graph databases causes persistent OBJECTSTORE_SOSTASK growth. - SQL Server Engine - Query Optimizer - All
• 5090699 - Fixes an issue in which a self-assignment update on a small off-row XML column by having compression enabled causes XML data corruption and a subsequent transport-level error when selecting the data. - SQL Server Engine - Access Methods - All
• 5126699 - Fixes an issue in which using the Oracle ODBC driver together with the ODBC connector in SSIS packages might cause heap corruption and data loss. - Integration Services - Integration Services - All
• 5130873 - Fixes a heap corruption issue in the generic ODBC connector when using the Oracle ODBC driver. - Integration Services - Integration Services - All
• 5131000 - Fixes an XML External Entity (XXE) vulnerability in the Web Service Task by blocking the file:// protocol in WSDL service endpoints to prevent unauthorized file access and denial-of-service attacks. - Integration Services - Integration Services - Windows
• 5157137 - Fixes CPU starvation issues by adding yields at regular intervals during in-memory OLTP garbage collection scan of hash indexes. - SQL Server Engine - In-Memory OLTP - All
• 5213660 - Fixes a back-up cleanup issue on Linux that could cause SQL Server to stop responding when a network share becomes full or unreachable. - SQL Server Engine - Linux - Linux

Original source

KB5080999 - Cumulative Update 24 for SQL Server 2022

Applies to: SQL Server 2022 on Windows, SQL Server 2022 on Linux

Release Date: March 12, 2026
Version: 16.0.4245.2

Summary

This article describes Cumulative Update package 24 (CU24) for Microsoft SQL Server 2022. This update contains 15 fixes that were issued after the release of SQL Server 2022 Cumulative Update 23. It updates components in the following builds:

• SQL Server - Product version: 16.0.4245.2, file version: 2022.160.4245.2
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

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 update

A downloadable Microsoft 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 2022, SQL Server 2019, and SQL Server 2017. 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 "#NNNNNNN" 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 table.

Improvements and fixes included in this update (table)

• 4838719 — Fixes an issue in StripedVdiTests to improve test reliability and stability. — SQL Server Engine — Backup Restore — Windows
• 4868211 — Adds a new optional parameter, @multi_subnet_failover, to sp_adddistributor. — SQL Server Engine — Replication — All
• 4874339 — Fixes an issue that occurs when creating or restoring a database on a contained availability group connection. — SQL Server Engine — High Availability and Disaster Recovery — All
• 4911747 — Fixes an issue in the in-memory sort buffer calculation that causes an infinite loop when the required page count exceeds supported limits. — SQL Server Engine — Backup Restore — All
• 4917971 — Fixes a floating point exception that occurs when switching from a Hekaton to a non-Hekaton stack. This action causes query execution to break. — Hekaton — Query Processing — All
• 4931278 — Fixes an issue in which a sort operation on a rowset that's larger than four billion rows fails and generates an assertion error. — SQL Server Engine — Access Methods — All
• 4931830 — Fixes an issue in which the distributor is part of an availability group (AG) and uses case-sensitive (_CS) collation. The distribution agent incorrectly uses the AG primary replica name instead of the AG listener name. — SQL Server Engine — Replication — All
• 4953763 — Fixes an issue in which the configure-only replica of a Contained Availability Group cannot be connected after a restart because of a startup failure. — SQL Server Engine — High Availability and Disaster Recovery — All
• 4955136 — Fixes an issue that occurs when using a local monitor server for Log Shipping and Contained Availability Group after failover. — SQL Server Engine — High Availability and Disaster Recovery — All
• 4955493 — Fixes a typo in sys.dm_os_linux_disk_stats by correcting ios_in_progess to ios_in_progress. — SQL Connectivity — Linux — Linux
• 4976761 — Fixes an issue in which altering a disabled DDL trigger causes a memory access violation. — SQL Server Engine — Programmability — All
• 4984502 — Adds a configurable full-text search batch timeout by using sp_fulltext_service 'batch_timeout'. Specify a value between one minute and one hour, in milliseconds. By default, batches time out after 10 minutes if there are no progress updates. — SQL Server Engine — Search — All
• 5005885 — Addresses contention on security-related metadata tables by adding sysowners to frequently accessed metadata tables check. — SQL Server Engine — Security Infrastructure — All
• 5011606 — Adds support for symbolic links in the getattribute API. — SQL Server Engine — Linux — Linux
• 5011720 — Adds a configuration option to add Bulkadmin operations to the allowlist. — SQL Server Engine — Linux — Linux

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

Prerequisites

Restart information

Registry information

Important notices

Hybrid environment deployment

Language support

Components (features) updated

Support for this update

How to uninstall this update

• How to uninstall this update on Windows
• How to uninstall this update on Linux

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

Original source

This article describes Cumulative Update package 4 (CU4) for Microsoft SQL Server 2022

This update contains 21 fixes that were issued after the release of SQL Server 2022 Cumulative Update 3, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4035.4, file version: 2022.160.4035.4
• Analysis Services - Product version: 16.0.43.211, file version: 2022.160.43.211

Known issues in this update

Issue one

After you install this cumulative update, external data sources using the generic ODBC connector may no longer work. When you try to query external tables that were created before installing this cumulative update, you receive the following error message:
Msg 7320, Level 16, State 110, Line 68
Cannot execute the query "Remote Query" against OLE DB provider "MSOLEDBSQL" for linked server "(null)". Object reference not set to an instance of an object.
If you try to create a new external table, you receive the following error message:
Msg 110813, Level 16, State 1, Line 64
Object reference not set to an instance of an object.
To work around this issue, you can uninstall this cumulative update or add the Driver keyword to the CONNECTION_OPTIONS argument. For more information, see Generic ODBC external data sources may not work after installing Cumulative Update.
This issue is fixed in SQL Server 2022 CU5.

Issue two

After you install this cumulative update, you may receive incorrect results from queries that meet all of the following conditions:

1. You have indexes that explicitly specify a descending sort order. Here's an example:
   CREATE NONCLUSTERED INDEX [nci_table_column1] ON [dbo].[table1] (column1 DESC)
2. You run queries against tables that contain these indexes. These queries specify a sort order that matches the sort order of the indexes.
3. The sort column is used in query predicates in the WHERE IN clause or multiple equality clauses. Here's an example:
   SELECT * FROM [dbo].[table1] WHERE column1 IN (1, 2) ORDER BY column1 DESC
   SELECT * FROM [dbo].[table1] WHERE column1 = 1 or column1 = 2 ORDER BY column1 DESC
   Note
   The IN clause that has a single value doesn't have this issue.
   To work around this issue, you can either uninstall this cumulative update or enable trace flag (TF) 13166 and then run DBCC FREEPROCCACHE.
   This issue is fixed in SQL Server 2022 CU5.

Issue three

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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references and descriptions]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

This article describes Cumulative Update package 5 (CU5) for Microsoft SQL Server 2022

This update contains 32 fixes that were issued after the release of SQL Server 2022 Cumulative Update 4, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4045.3, file version: 2022.160.4045.3
• Analysis Services - Product version: 16.0.43.218, file version: 2022.160.43.218

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.

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 2022, SQL Server 2019, and SQL Server 2017.

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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references, descriptions, fix areas, components, and platforms]

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

Last updated on 05/30/2025

Original source

This article describes Cumulative Update package 6 (CU6) for Microsoft SQL Server 2022

This update contains 15 fixes that were issued after the release of SQL Server 2022 Cumulative Update 5, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4055.4, file version: 2022.160.4055.4
• Analysis Services - Product version: 16.0.43.219, file version: 2022.160.43.219

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 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 2022, 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 "#NNNNNNN" 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.

Improvements and fixes included in this update table (selected entries):

• 2439381: Fixes potential memory access violations and incorrect results when executing specific Data Analysis Expressions (DAX) queries that trigger the internal Horizontal Fusion query optimization. Note: Before you apply the cumulative update, you can disable the feature by setting the DAX\HorizontalFusion configuration option to 0 as a workaround.
• 2442140: Fixes an issue in which an alias error occurs during a database upgrade if you apply the name "en" to an attribute.
• 2424714: Fixes a non-yielding scheduler condition (Msg 17883) that you encounter when backup operations can't handle abort signals correctly in some cases while waiting for pending I/O writes.
• 2449506: Fixes an issue in which the SQL Server instance stops responding when it calls a memory-optimized stored procedure from another memory-optimized stored procedure in which the called procedure isn't yet in the plan cache, and a statistics update is triggered during query compilation.
• 2382857: Fixes an issue in which the node profile information from parallel threads for Cardinality Estimation (CE) feedback is missing. After you apply this fix, CE feedback can suggest hints for parallel queries.
• 2470755: Fixes an access violation that you encounter under a race condition if the parameter sensitive plan (PSP) optimization feature has Query Store integration enabled, and a query variant's reference to its associated dispatcher or original parent statement is dereferenced prematurely within the in-memory representation of the Query Store.
• 2434843: Fixes an issue in which a thread deadlock between Query Store (QDS) background tasks blocks the database shutdown.
• 2266818: Adds a new error 673 that helps avoid the assertion failure (Location: IndexRowScanner.cpp:1449; Expression: m_versionStatus.IsVisible ()) that you might encounter when you enable change tracking on a database that has snapshot isolation turned on. Error message: Failure to access row object in snapshot isolation. Note: You need to turn on trace flag 8285.
• 2442348: Fixes an issue in which applying a patch on the secondary replica or performing an in-place upgrade fails if a database has change data capture (CDC) enabled and is in an availability group. The following error is returned: Error: 912, Severity: 21, State: 2. Script level upgrade for database 'master' failed because upgrade step 'repl_upgrade.sql' encountered error 35262, state 4, severity 10. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
• 2397656: FIX: SQL Server Audit Events fail to write to the Security log (KB4052136)
• 2472403: Fixes the following error 41313 that you encounter when you create a natively compiled stored procedure that contains a CASE statement and a column that uses dynamic data masking (DDM): Msg 41313, Level 16, State 1, Procedure , Line [Batch Start Line ] The C compiler encountered a failure. The exit code was 2.
• 2475171: Enables Microsoft Entra authentication for SQL Server replication. Microsoft Entra authentication for replication can be disabled by using trace flag 11561. Using Microsoft Entra authentication for replication is currently in public preview. For more information, see Configure replication with Microsoft Entra authentication.
• 2405773: Fixes an issue in which upgrading SQL Server 2017 to SQL Server 2022 on Linux fails and returns an error such as "'model_replicatedmaster.ldf' file does not exist."
• 2425643: Fixes an issue in which running DBCC CHECKDB reports RBPEX::NotifyFileShutdown in the SQL Server error log.
• 2431805: Fixes a non-yielding dump issue that you encounter when the IORequestDispenser is waiting for the I/O to finish.

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

Summary

This article describes Cumulative Update package 7 (CU7) for Microsoft SQL Server 2022. This update contains 20 fixes that were issued after the release of SQL Server 2022 Cumulative Update 6, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4065.3, file version: 2022.160.4065.3
• Analysis Services - Product version: 16.0.43.221, file version: 2022.160.43.221

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 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 2022, 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 "#NNNNNNN" 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.

[Table of Improvements and fixes included in this update with bug references, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

[Instructions and links for obtaining or downloading the update]

File information

[File hash information and cumulative update package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling this update on Windows and Linux]

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

Original source

This article describes Cumulative Update package 8 (CU8) for Microsoft SQL Server 2022

This update contains 12 fixes that were issued after the release of SQL Server 2022 Cumulative Update 7, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4075.1, file version: 2022.160.4075.1
• Analysis Services - Product version: 16.0.43.221, file version: 2022.160.43.221

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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

[Instructions and links for obtaining or downloading the update for Windows and Linux]

File information

[File hash information and cumulative update package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling this update on Windows and Linux]

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

Original source

This article describes Cumulative Update package 9 (CU9) for Microsoft SQL Server 2022. This update contains 26 fixes that were issued after the release of SQL Server 2022 Cumulative Update 8, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4085.2, file version: 2022.160.4085.2
• Analysis Services - Product version: 16.0.43.222, file version: 2022.160.43.222

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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references, descriptions, fix areas, components, and platforms]

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

Original source

Cumulative Update package 10 (CU10) for Microsoft SQL Server 2022

This article describes Cumulative Update package 10 (CU10) for Microsoft SQL Server 2022. This update contains 9 fixes that were issued after the release of SQL Server 2022 Cumulative Update 9, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4095.4, file version: 2022.160.4095.4
• Analysis Services - Product version: 16.0.43.222, file version: 2022.160.43.222

Known issues in this update

Issue one: Read-scale availability group not displayed in dm_hadr_database_replica_cluster_states
SQL Server 2022 CU10 introduced fix 2714261, which causes an issue with sys.dm_hadr_database_replica_cluster_states for read-scale availability groups that results in the Availability Databases folder in SQL Server Management Studio (SSMS) not showing the databases in the availability group (AG). To mitigate this issue, roll back the patch to CU9.
This issue is fixed in SQL Server 2022 CU12.

Issue two: 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 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 2022, 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 "#NNNNNNN" 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 2751378: Fixes an access violation dump issue that you encounter when you run a query on the clustered columnstore table that uses the READPAST hint.
• Bug reference 2732520: Before this update, in some rare cases, if IDENTITY_INSERT is set to ON, the identity value for the target table is set to the highest value in the source table when joining tables, even if the highest value doesn't satisfy the join condition or the predicate. This update improves the current design and fixes this issue. Note: To apply this update, you need to set the QUERY_OPTIMIZER_HOTFIXES database scoped configuration to ON. To turn off this update, you can enable trace flag 13193.
• Bug reference 2714261: Fixes unexpected characters that you encounter in the name column of the sys.availability_groups_cluster dynamic management view (DMV) when you use the read-scale availability group.
• Bug reference 2645943: Fixes an issue in which running sys.dm_db_xtp_transactions might fail with the following error if a large number of transactions are in the In-Memory OLTP database engine: Msg 701, Level 17, State 157, Line There is insufficient system memory in resource pool 'default' to run this query.
• Bug reference 2712771: Fixes an issue in which the exported delimited text file always uses a comma (',') as the field terminator when you use CREATE EXTERNAL TABLE AS SELECT (CETAS) to export data to a delimited text file, even if the FIELD_TERMINATOR character is specified in CREATE EXTERNAL FILE FORMAT.
• Bug reference 2698036: The Log Reader Agent creates a dynamic linked server for the listener to verify the metadata when you configure a transactional publication on an Always On availability group (AG). This dynamic linked server is temporary and dropped after the verification. When the AG is deployed with replicas in different subnets, this dynamic linked server connection might time out as it tries to connect serially. After applying the fix, if the Log Reader Agent is configured to use the MultiSubnetFailover parameter as 1, the dynamic linked server is also created with the MultiSubnetFailover parameter as 1, which allows connection to occur in parallel.
• Bug reference 2695485: Fixes the following error that you encounter on the target instance when configuring a Service Broker communication with transport security and the certificate serial number length is greater than 16 bytes: The certificate serial number size is 19, however it must be no greater than 16 bytes in length. This occurred in the message with Conversation ID, Initiator: 1, and Message sequence number: 0.
• Bug reference 2606378: Updates the errors 1101 and 1105 to explicitly reflect the fact that even UNLIMITED database files are limited to 16 TB. Error message: 1101: Could not allocate a new page for database '' because the '' filegroup is full due to lack of storage space or database files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 1105: Could not allocate space for object '' in database '' because the '' filegroup is full due to lack of storage space or database files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
• Bug reference 2726328: Fixes an assertion failure (Location: "cxrowset.cpp":2006; Expression: cstePrefix >= 1) that you encounter when updating statistics fails with the following error: Msg 3624, Level 20, State 1, Line A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.

Original source

This article describes Cumulative Update package 11 (CU11) for Microsoft SQL Server 2022. This update contains 16 fixes that were issued after the release of SQL Server 2022 Cumulative Update 10, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4105.2, file version: 2022.160.4105.2
• Analysis Services - Product version: 16.0.43.222, file version: 2022.160.43.222

Known issues in this update

Issue one: Read-scale availability group not displayed in dm_hadr_database_replica_cluster_states

SQL Server 2022 CU10 introduced fix 2714261, which causes an issue with sys.dm_hadr_database_replica_cluster_states for read-scale availability groups that results in the Availability Databases folder in SQL Server Management Studio (SSMS) not showing the databases in the availability group (AG). To mitigate this issue, roll back the patch to CU9.
This issue is fixed in SQL Server 2022 CU12.

Issue two: 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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes with Bug reference, Description, Fix area, Component, Platform]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

[Instructions and links for obtaining or downloading the update]

File information

[File hash information and cumulative update package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling this update on Windows and Linux]

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

Additional resources

Training

Module
Get started with SQL Server 2025 - Training
Learn about SQL Server 2025's new capabilities including AI integration, analytics improvements, developer features, and performance enhancements.

Certification

Microsoft Certified: Azure Database Administrator Associate - Certifications
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.

Last updated on 05/30/2025

• SQL Server - Product version: 16.0.4115.5, file version: 2022.160.4115.5
• Analysis Services - Product version: 16.0.43.229, file version: 2022.160.43.229

Note
SQL Server 2022 CU6 enabled Microsoft Entra authentication for SQL Server replication. After you install SQL Server 2022 CU12, this feature will be generally available. For more information, see Configure replication with Microsoft Entra authentication.

Microsoft Entra authentication for replication can be disabled by using trace flag 11561.

Original source

Known issues in this update

Issue one: Patching error for secondary replicas in an availability group with databases enabled replication, CDC, or SSISDB

SQL Server 2022 CU13 introduced fix 2998350 to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication or change data capture (CDC) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.

After SQL Server Setup initially fails, the SQL Server service then tries to come online again without single-user mode. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required.

The patch fails with the following error:
Error installing SQL Server Database Engine Services Instance Features
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error code: 0x851A001A

When you check the SQL Server error log, you see a message with an invalid Group ID. To verify it's an invalid ID, look for previous startup records in the same log file for the problematic database name to compare:
Skipping the default startup of database because the database belongs to an availability group (Group ID: ). The database will be started by the availability group. This is an informational message only. No user action is required.

If you want to prevent the patch from reporting an initial failure, you can perform one of the following actions before running the patch:

• Enable Trace Flag 12347 - reverts the changes made in fix 2998350. You should remove this trace flag after patching.
• Drop the CDC or replication enabled database from the AG.
• Remove CDC or replication from the database in the AG.

This issue is fixed in SQL Server 2022 CU16.

Issue two: 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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references and descriptions]

How to obtain or download this or the latest cumulative update package

[Instructions and links for obtaining the update]

File information

[File hash and package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling on Windows and Linux]

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

Original source

This article describes Cumulative Update package 14 (CU14) for Microsoft SQL Server 2022. This update contains 12 fixes that were issued after the release of SQL Server 2022 Cumulative Update 13, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4135.4, file version: 2022.160.4135.4
• Analysis Services - Product version: 16.0.43.233, file version: 2022.160.43.233

Known issues in this update

Issue one: Patching error for secondary replicas in an availability group with databases enabled replication or CDC

SQL Server 2022 CU13 introduced fix 2998350 to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication or change data capture (CDC) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.

After SQL Server Setup initially fails, the SQL Server service then tries to come online again without single-user mode. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required.

The patch fails with the following error:
Error installing SQL Server Database Engine Services Instance Features
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error code: 0x851A001A

When you check the SQL Server error log, you see a message with an invalid Group ID. To verify it's an invalid ID, look for previous startup records in the same log file for the problematic database name to compare:
Skipping the default startup of database because the database belongs to an availability group (Group ID: ). The database will be started by the availability group. This is an informational message only. No user action is required.

If you want to prevent the patch from reporting an initial failure, you can perform one of the following actions before running the patch:

• Enable Trace Flag 12347 - reverts the changes made in fix 2998350. You should remove this trace flag after patching.
• Drop the CDC or replication enabled database from the AG.
• Remove CDC or replication from the database in the AG.

This issue is fixed in SQL Server 2022 CU16.

Issue two: SQL Server VSS Writer might fail to perform a backup because no database is available to freeze

When backup tools such as Azure Recovery Vault perform a backup on a virtual machine (VM), they might fail to achieve application consistency. There might not be any errors. The application runs fast without any backups being done. The SQL Server Volume Shadow Copy Service (VSS) Writer ends up in a non-retryable error state. If you enable SQL Server VSS Writer trace, you might see the following exception, which indicates there's no database to freeze, resulting in an unsuccessful snapshot:
[0543739500,0x002948:011b4:0xb87fa68e] sqlwriter.yukon\sqllib\snapsql.cpp(1058): Snapshot::Prepare: Server PROD-SQL01 has no databases to freeze
Additionally, some databases might be detected with Online:0:
[0543739390,0x002948:0x11b4:0xb87fa68e] sqlwriter.yukon\sqllib\snapsql.cpp(0408): FrozenServer::FindDatabases2000: Examining database
Online:0 Standby:0 AutoClose:0 Closed:0

If you use Azure Recovery Vault, you might see an error like the following one in the event list:
App-consistent recovery point generation failed.

The issue arises from a code change in SQL Server 2022 CU14 that checks if a database is online and ready to be frozen. The current solution is to roll back to SQL Server 2022 CU13 and perform the snapshot backup. For more information about how to roll back the package to a previous version, see Uninstall a Cumulative Update from SQL Server.

This issue is fixed in SQL Server 2022 CU15.

Issue three: 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 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 2022, 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 "#NNNNNNN" 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 3217208 Starting with SQL Server 2022 (16.x) CU14, container images include the new mssql-tools18 package. The previous directory /opt/mssql-tools/bin is phased out. The new directory for Microsoft ODBC 18 tools is /opt/mssql-tools18/bin, aligning with the latest tools offering. For more information about changes and security enhancements, see ODBC Driver 18.0 for SQL Server Released. SQL Server Client Tools Command Line Tools Linux 3110961 Fixes an issue in which maintenance plan logs might report garbled characters when the message reported involves non-ASCII characters. SQL Server Client Tools Management Services Windows 3278705 Fixes the following error that you encounter during a Volume Shadow Copy Service (VSS) restore on a SQL Server instance that has previously deleted databases: Volume Shadow Copy Service error: Unexpected error calling routine GetVolumePathName is fail on the path ... The system cannot find the file specified. SQL Server Engine Backup Restore Windows 3285752 Fixes an issue in which the SQL Server Launchpad service can't shut down properly when certain errors occur during startup. SQL Server Engine Extensibility Windows 2897811 Fixes an issue in which the remote secondary replica shows Not Synchronizing for several minutes after successive failovers between local replicas. It occurs when configured in multi-subnet, multi-region configurations in the cloud with two or more local replicas and one or more remote replicas. SQL Server Engine High Availability and Disaster Recovery Windows 3088149 Fixes an assertion dump issue (Location: hadrlogcapture.cpp:; Expression: m_pFsManager->GetEnqueuedBlockId () < capturedLogBlockId capturedLogBlockId == m_pDbPartner->GetFirstLogBlockIdToCapture ()) that you encounter when there are FILESTREAM transactions in an Always On availability group (AG). SQL Server Engine 3157066 Adds performance monitor counters to the cluster log report when the health check timeout is reported. SQL Server Engine High Availability and Disaster Recovery Windows 3207515 FIX: Memory exceeds the configured limits that are specified by memory.memorylimitmb in SQL Server (KB5042369) SQL Server Engine Linux Linux 3155852 Fixes an assertion failure (Location: sosmemobj.cpp:2744; Expression: pvb->FInUse()) in CVariableInfo::PviRelease that you encounter when you use UTF-8 collations and the WITH RESULT SETS clause. SQL Server Engine Programmability All 3157452 Fixes two issues related to cardinality estimation (CE) feedback: plan cache leaks and access violations due to race conditions with statement recompilations. SQL Server Engine Query Optimizer All 3236328 Improves cardinality estimation (CE) for predicates that request ranges disjoint with column statistics when statistics have only one histogram step. SQL Server Engine Query Optimizer All 3222639 Fixes an issue in which change tracking auto cleanup consumes CPU in cycles every 30 minutes even if change tracking isn't enabled on any databases. Note: After applying the fix, if you see some rows in sys.syscommittab or dbo.MSchange_tracking_history tables in databases where change tracking is disabled, you need to re-enable and then disable change tracking on these databases. This will clean all tracking data. For more information, see Enable and Disable Change Tracking. SQL Server Engine Replication All

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

KB5041321 - Cumulative Update 15 for SQL Server 2022

Applies to: SQL Server 2022 on Windows, SQL Server 2022 on Linux
Release Date: September 25, 2024
Version: 16.0.4145.4

Summary

This article describes Cumulative Update package 15 (CU15) for Microsoft SQL Server 2022. This update contains 14 fixes that were issued after the release of SQL Server 2022 Cumulative Update 14, and it updates components in the following builds:

• SQL Server - Product version: 16.0.4145.4, file version: 2022.160.4145.4
• Analysis Services - Product version: 16.0.43.233, file version: 2022.160.43.233

Known issues in this update

Issue one: Patching error for secondary replicas in an availability group with databases enabled replication or CDC
SQL Server 2022 CU13 introduced fix 2998350 to make secondary databases in an availability group (AG) startup more reliably. However, this fix causes a problem where AG databases don't start recovery if SQL Server is running in single-user mode. SQL Server Setup runs in single-user mode. As a result of this, if you run Setup and also have SQL replication or change data capture (CDC) enabled on a database in the AG, when the catalog upgrade scripts try to run but can't access the database, setup fails.
After SQL Server Setup initially fails, the SQL Server service then tries to come online again without single-user mode. At that time, the patch upgrade scripts finish successfully and patching is complete. Once startup completes, the issue is resolved and no user action is required.
The patch fails with the following error:
Error installing SQL Server Database Engine Services Instance Features
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error code: 0x851A001A
When you check the SQL Server error log, you see a message with an invalid Group ID. To verify it's an invalid ID, look for previous startup records in the same log file for the problematic database name to compare:
Skipping the default startup of database because the database belongs to an availability group (Group ID: ). The database will be started by the availability group. This is an informational message only. No user action is required.
If you want to prevent the patch from reporting an initial failure, you can perform one of the following actions before running the patch:

• Enable Trace Flag 12347 - reverts the changes made in fix 2998350. You should remove this trace flag after patching.
• Drop the CDC or replication enabled database from the AG.
• Remove CDC or replication from the database in the AG.
  This issue is fixed in SQL Server 2022 CU16.

Issue two: 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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes and improvements with bug references, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

[Instructions and links for obtaining or downloading the update for Windows and Linux]

File information

[File hash information and cumulative update package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling this update on Windows and Linux]

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

Additional resources

Training
Certification
Microsoft Certified: Azure Database Administrator Associate - Certifications
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.

Last updated on 05/30/2025

Original source

Release information

• Applies to: SQL Server 2022 on Windows, SQL Server 2022 on Linux
• Release Date: November 14, 2024
• Version: 16.0.4165.4

Summary

This article describes Cumulative Update package 16 (CU16) for Microsoft SQL Server 2022. This update contains 16 fixes that were issued after the release of SQL Server 2022 Cumulative Update 15 and it updates components in the following builds:

• SQL Server - Product version: 16.0.4165.4, file version: 2022.160.4165.4
• Analysis Services - Product version: 16.0.43.239, file version: 2022.160.43.239

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 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 2022, 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 "#NNNNNNN" 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.

[Table of fixes with bug references, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

[Instructions and links for obtaining the update]

File information

[File hash information and cumulative update package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling on Windows and Linux]

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

Last updated on 05/30/2025

Original source