Note
Access to this page requires authorization. You can try signing in or .
Access to this page requires authorization. You can try .
KB5031778 - Cumulative Update 10 for SQL Server 2022
Release Date: November 16, 2023
Version: 16.0.4095.4
Summary
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 | Description | Fix area | Component | Platform |
|---|---|---|---|---|
| 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. |
SQL Server Engine | Column Stores | All |
| 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. |
SQL Server Engine | DB Management | All |
| 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. |
SQL Server Engine | High Availability and Disaster Recovery | All |
| 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 <LineNumber> There is insufficient system memory in resource pool 'default' to run this query. |
SQL Server Engine | In-Memory OLTP | All |
| 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. |
SQL Server Engine | PolyBase | All |
| 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. |
SQL Server Engine | Replication | Windows |
| 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. |
SQL Server Engine | SQL Server Engine | All |
| 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 '<DatabaseName>' because the '<FilegroupName>' 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 '<ObjectName>' in database '<DatabaseName>' because the '<FilegroupName>' 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. |
SQL Server Engine | Storage Management | All |
| 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 <LineNumber> 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. |
SQL Server Engine | Table Index Partition | 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
- 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?
