Microsoft SQL Server 2022 CU1

- Fixes error 35221 that occurs in the following scenarios: - You attempt to add a file to a FILESTREAM filegroup or a memory-optimized filegroup. - You attempt to add additional transaction log files to a database. Error message: Msg 35221, Level 16, State 1, Line <LineNumber> Could not process the operation. Always On Availability Groups replica manager is disabled on this instance of SQL Server. Enable Always On Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.
- Fixes a self-deadlock issue where internal update statistic transactions persist locks, which can cause unresolved deadlocks with user queries. The issue occurs because the lock isn't released when the system runs the update query statistics. After you apply this fix, the lock can be released as intended.
- Fixes an access violation exception that occurs on the primary replica when the secondary replica sends cursor plans to the primary replica for storage in Query Store (QDS).
- Updates Microsoft.Data.SqlClient assemblies used by the mashup engine to address security vulnerability discussed in CVE-2022-41064.
- This fix is a safeguard for issues that can cause unavailability due to memory capacity in some rare queries (nested queries performing table scans). Before issuing these queries, it tries to make sure sufficient space is available and avoids causing any further capacity issues.
- Fixes an issue with differential backup skipping new Page Free Space (PFS) pages after a data file grows around a PFS boundary (a multiple of 8,088 pages; 64,704 KB), resulting in database corruption and a possible crash dump when this differential backup is restored.
- Enhances the encryption algorithm that's used to encrypt data sources and connection strings in SQL Server Analysis Services (SSAS) models. For more information, see Upgrade encryption.
- Fixes an assertion failure that occurs in natively compiled modules when the Inner FOR JSON operator is followed by an operator that buffers the corresponding objects, such as another FOR JSON or ORDER BY operator. Additionally, you may see the following assert expression: Location:     memilb.cpp:<LineNumber> Expression: (*ppilb)->m_cRef == 0 SPID:         <SPID> Process ID:    <ProcessID>
- Fixes an assertion failure (Location: execcoll.cpp:1317; Expression: ‘savepointId > HkTxSavePointDefault’) that occurs during the savepoint cleanup in a Hekaton transaction.
- Fixes an issue where the Transact-SQL snapshot backup fails with the following errors when a database is suspended in single-user mode: Msg 3081, Level 16, State 9, Line <LineNumber> Database <'DatabaseName'> was previously suspended for snapshot backup. Msg 5069, Level 16, State 1, Line <LineNumber> ALTER DATABASE statement failed.
- Fixes an access violation and INVALID_POINTER_READ_CPP_EXCEPTION_c0000005_sqldk.dll!ex_oomCheck exceptions triggered by an out-of-memory (OOM) exception when the SQL Server instance is under memory pressure.
- This fix is a safeguard for issues that can cause unavailability due to memory capacity in some rare queries (nested queries performing table scans). Before issuing these queries, it tries to make sure sufficient space is available and avoids causing any further capacity issues.
- Reverts the length of ROUTINE_DEFINITION column to 4000 in the INFORMATION_SCHEMA.ROUTINES view as the previous change in the length may cause unexpected inconsistencies.
- Fixes an issue where In-Memory OLTP stored procedures that have streaming table-valued functions (STVFs), expressions, or constraint checks may generate inconsistent query plan hashes.
- Fixes an issue where the Distribution Agent returns a general message code 20046 instead of the connection failure message code 20084 when it fails to connect to the Subscriber by using the non-cached connection. These errors are specific to the Replication Distribution Agent. Error message: 20046: The process encountered a general external error. 20084: The process could not connect to server.
- Fixes a failure to raise the proper data type overflow error when a comma-separated values (CSV) file has an integer (int) value larger than the maximum value of int and you run SELECT <integer_column_name> FROM OPENROWSET on this CSV file.
- Removes a case of multiple inheritance in the RSA encryption code in SQL Server 2022.
- Fixes a spelling issue in error 33025 (Invalid cryptographic provider property: %S_MSG) when you use the Extensible Key Management (EKM) feature.
- Fixes the following error that can occur when you load audit logs from SQL Server Management Studio (SSMS): Item has already been added. Key in dictionary: 'MNDO' Key being added: 'MNDO'
- Before you apply this update, the key name in the JSON_OBJECT function output isn't quoted when the data type is a numeric, Boolean, or internal JSON data type. After you apply this update, keys in JSON_OBJECT are quoted.
- FIX: Database accessibility issues with high-volume customer workloads that use EKM for encryption and key generation
- Improvement: Automatically enables the binary large object (BLOB) trace ring buffer feature when a BLOB assertion failure is detected. This improvement helps to better investigate such issues.
- Fixes a rare issue where memory corruption in the ODBC driver can occur in communications between two SQL Server instances. This issue occurs when the target SQL Server instance uses a down-level version of the Tabular Data Stream (TDS) protocol. An improper version check causes image data types to be decoded improperly on the client-side of the connection.
- Enhancement: Split the FT_IFTS_RWLOCK wait type into more granular wait types for more accurate diagnostics of the problem. For more information about these wait types, see sys.dm_os_wait_stats (Transact-SQL).
- Adds a new sys.dm_external_provider_certificate_info dynamic management view (DMV), which returns information about the Azure cloud certificates used in SQL Server to set up and maintain an Azure Active Directory (Azure AD) administrator for Azure AD authentication. For more information, see sys.dm_external_provider_certificate_info (Transact-SQL).
- Fixes error 8992 [Check Catalog Msg 3853, State 1: Attribute (owning_principal_id=<ID>) of row (principal_id=<ID>) in sys.database_principals does not have a matching row (principal_id=<ID>) in sys.database_principals.] generated by DBCC CHECKDB when executed against a database clone of a change data capture (CDC) enabled source database that has system-defined roles owned by CDC users.
- Resolves a query performance issue that affects change tracking autocleanup and manual cleanup queries. Note You need to turn on trace flags 8286 and 8287, as this forces the cleanup query to use the FORCE ORDER and FORCESEEK hints to speed up the performance.
- Fixes the following issues with attribute-based policies of Purview - Azure Attribute-based access control (Azure ABAC):  - Attributes don't synchronize correctly. - The synchronization process can't move past the table that didn't have attribute synchronization. - On retry, the synchronization process encounters exceptions because it expected the database state to be planning not synchronization.
- Fixes a DBCC CLONEDATABASE failure when upgrading the source database from an earlier version of SQL Server.
- Fixes an issue where schema modification (Sch-M) locks are acquired on foreign key tables when altering columns on the primary tables even if the transaction isn't related to the foreign key column. After you apply this fix, SQL Server only acquires schema stability (Sch-S) locks on foreign key tables. For more information, see Schema locks.
- Fixes a primary key violation error that's caused by a timing issue in change data capture (CDC) in SQL Server 2022. The CDC capture process may try to insert a duplicate start_lsn value in the cdc.lsn_time_mapping table, and you may see an error message that resembles the following one: Violation of PRIMARY KEY constraint 'lsn_time_mapping_clustered_idx'. Cannot insert duplicate key in object 'cdc.lsn_time_mapping'. The duplicate key value is (Value). Note This fix covers all the causes of this error. For the same issue that occurs in SQL Server 2019 that has a previous cumulative update installed, SQL Server 2017, and SQL Server 2016, see the previous fix KB 4521739. However, the previous fix didn't cover all the cases.
- Fixes error 302 in SQL Server replication. When the Distribution Agent attempts to apply a snapshot generated on a table that has a primary key with the NEWSEQUENTIALID function as a default value, the following error occurs: Msg 302, Severity 16 The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type 'uniqueidentifier' in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression.
- Improvement: The sp_invoke_external_rest_endpoint stored procedure is only supported in Azure SQL Database environments. If you try to use this procedure in on-premises environments, you'll receive a spurious error like the following one: Msg 2812, Level 16, State 99, Procedure sys.sp_invoke_external_rest_endpoint_internal, Line <LineNumber> [Batch Start Line <LineNumber>] Could not find stored procedure 'sp_invoke_external_rest_endpoint_internal'. The fix improves the message to read as follows: "sp_invoke_external_rest_endpoint" is not supported on this edition of SQL Server.
- Fixes error 241 that occurs while running the Snapshot Agent, and the system date format was changed to a different format than the one used by SQL Server. Error message: Conversion failed when converting date and/or time from character string.
- Fixes an issue where a memory dump may occur in CMIterStatsDisk::GetNextStatForLeadingColumn caused by some metadata inconsistencies.
- Fixes an issue where the Azure Active Directory (Azure AD) administrator isn't added to the sysadmin group after you configure Azure AD for SQL Server 2022
- Updates the error message 37517 used for the Microsoft Purview access policies in SQL Server to the following one: Internal error occurred while obtaining ARC resource information from IMDS endpoint. Substate: '%ls', status: 0x%08x.
- Fixes an exception that generates a dump file when using Microsoft Purview access policies for SQL Server 2022 and running the sp_external_policy_refresh stored procedure as a non-admin Azure Active Directory (Azure AD) user.
- Fixes an issue where the temporary linked server created by the Log Reader Agent isn't always properly dropped when the publisher is in an Always On availability group (AG) and there's a failover at the distributor. After you apply this fix, the linked server is properly removed.
- Fixes an issue where Full-text Search generates memory leaks and high waits in full-text queries.
- This fix resolves the following issues that can occur when you rename databases: Issue 1: SQL Server crashes when a user who has a non-default schema (for example: CREATE USER <user_name> FOR LOGIN <login_name> WITH DEFAULT_SCHEMA = <schema_name>) executes queries in the following sequence: 1. Executes a query like the following with an implicit name (a schema name that isn't explicitly specified requires SQL Server to determine the same name): SELECT * FROM <database_name>..<table_name> 2. Renames the database. 3. Reruns the implicit query from step 1. Issue 2: Fixes SQL Server error 942 that occurs when you perform the following steps in the same sequence on your SQL Server instance: 1. You query a table in a database (for example: SELECT * FROM DatabaseA.sys.columns). 2. You rename an existing database (for example: ALTER DATABASE DatabaseA MODIFY NAME = DatabaseA_old). 3. You take this renamed database offline (for example: ALTER DATABASE DatabaseA_old SET OFFLINE). 4. You rename another database on the - server to have the same name as the database that you renamed in step 2 (for example: ALTER DATABASE DatabaseA_new MODIFY NAME = DatabaseA). 5. Now if you query a table in this database (for example: SELECT * FROM DatabaseA.sys.columns), you'll receive the following 942 error: Msg 942, Level 14, State 4, Line <LineNumber> Database 'DatabaseA_old' cannot be opened because it is offline.
- This update removes the requirement for the trace flag (TF) 809 for the hybrid buffer pool with direct write feature. After you apply this update, this feature is enabled by default in SQL Server 2022. This update introduces TF 898 to disable the Direct Write behavior of the hybrid buffer pool for troubleshooting or debugging purposes.
- Fixes error 41842 that's incorrectly shown even when natively compiled stored procedures or in-memory transactions don't insert many records in a single transaction. Here's the error message: Error 41842: Too many rows inserted or updated in this transaction. You can insert or update at most 4,294,967,294 rows in memory-optimized tables in a single transaction.
- Fixes a high CPU usage condition that occurs when you enable change tracking on a large number of tables and do automatic or manual cleanup of the change tracking tables.
- Fixes errors 12300 (Computed columns are not supported) and 12301 (Nullable columns in the index key are not supported) when transactional replication is enabled on memory optimized tables with computed columns and the index on nullable columns respectively. After applying this fix, you can enable transactional replication on memory optimized tables with computed columns and the index on nullable columns.
- Fixes the following error that occurs when you try to start the SQL Server Import and Export Wizard after you install the SQL Server Database Engine: An error occurred which the SQL Server Integration Services Wizard was not prepared to handle. (SQL Server Import and Export Wizard) =================================== Could not load file or assembly 'Microsoft.DataTransformationServices.ScaleHelper, Version=16.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (DTSWizard)
- Fixes error 8657 when running queries that use percentile mode for memory grant feedback.
- Fixes spelling issues in Database Engine error messages in SQL Server 2022.
- Fixes "The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x00 is unknown" error that occurs when using the strict encryption option in your connection settings. For an example about this scenario, see Invalid TDS Stream errors with Encrypt=Strict when executing Stored Procedures.
- FIX: Scalar UDF Inlining issues in SQL Server 2022 and 2019
- Consider the following scenario: - You have a transactional replication setup. - You execute the sp_changearticle stored procedure to change the property of an article on the publisher, and data manipulation language (DML) changes occur on the published table. In this scenario, the Log Reader Agent reader thread may generate the following assertion dump when processing the log records: * Location: replrowset.cpp:<LineNumber> * Expression: (LSN)m_curLSN < (LSN)(pSchemas->schema_lsn_begin) * SPID: <SPID> * Process ID: <ProcessID>
- After you apply this update, you can audit events (EXTERNAL GOVERNANCE TURNED ON and EXTERNAL GOVERNANCE TURNED OFF) that correspond to external governance enable/disable actions (Microsoft Purview access policies). The correctness of audit records is ensured when evaluating data reader and writer permissions. This update introduces trace flag (TF) 12481 to disable logging auditing information for external permissions in the external_policy_permission_checked field of audit records.
- Fixes a gradual memory leak in the SQL Server process (the high usage under MEMORYCLERK_SOSNODE) caused by the Log Reader Agent in transactional replication.
- Fixes an issue where Database Mail fails to send email messages and logs the following error message in the SQL Server error log, when used in a contained availability group (AG): The activated proc '[dbo].[sp_sysmail_activate]' running on queue '<DatabaseName>_msdb.dbo.ExternalMailQueue' output the following: 'Cannot find the object 'ExternalMailQueue' because it does not exist or you do not have permissions.'
- Fixes an issue where the read query on a readable secondary replica may be aborted or return unexpected results if the query uses a heap and forwarding records are present in the heap.
- Fixes the following error that occurs when running the change data capture (CDC) Control task fails: Could not load file or assembly 'Microsoft.SqlServer.DtsMsg, Version=16.100.0.0,Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.(Exception from HRESULT: 0x80131040)
- 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.
- Fixes an exception that occurs when JSON_ARRAY/JSON_OBJECT return values are used in a parameter in functions that take strings. After you apply this fix, return values of JSON_ARRAY and JSON_OBJECT are made coercible and can be used as string parameters.
- Fixes an issue where any member who has the DQS KB Operator (dqs_kb_operator) role or a higher privilege level role can create or overwrite arbitrary files on the machine hosting SQL Server as the account that runs the SQL Server service (the default account is NT SERVICE\MSSQLSERVER).
- Fixes index inconsistency or incorrect results that may occur in the following scenario: 1. You enable accelerated database recovery (ADR) and snapshot isolation. 2. You roll back to a savepoint. 3. You update on top of aborted rows and the version cleanup lags behind this update.
- Fixes an issue where an authenticated attacker could affect SQL Server memory when executing a specially crafted CREATE STATISTICS or UPDATE STATISTICS statement.
- After you apply this update, you need at least the control server permission to run the procedure sys.sp_xtp_force_gc. This update changes the implementation of the procedure to a single call for allocated and used bytes to be freed. Before you apply this update, you need to call it twice. For more information, see Gradual increase in XTP memory consumption.
- Adds the queries and category of the Microsoft Customer Experience Improvement Program (CEIP) telemetry to SQL Server 2022.
- Fixes an issue where any member who has the DQS KB Operator (dqs_kb_operator) role or a higher privilege level role can create or overwrite arbitrary files on the machine hosting SQL Server as the account that runs the SQL Server service (the default account is NT SERVICE\MSSQLSERVER).
- An authenticated attacker could affect SQL Server memory when running a specially crafted CREATE or UPDATE STATISTICS statement.
- Any member who has the DQS KB Operator (dqs_kb_operator) role or a higher privilege-level role can run codes on the computer that's hosting SQL Server as the account that's running the SQL Server service (default account is NT SERVICE\MSSQLSERVER).
- Error when running remote procedure call (RPC) over strict connections.
- In rare circumstances, a memory corruption in the ODBC driver can occur in communications between two SQL Server-based servers. This issue occurs if the target SQL server uses a down-level version of the Tabular Data Stream (TDS) protocol. An improper version check causes image data types to be decoded incorrectly on the client-side of the connection.
- Any member who has the DQS KB Operator (dqs_kb_operator) role or a higher privilege-level role can create or overwrite arbitrary files on the computer that's hosting SQL Server as the account that's running the SQL Server service (default account is NT SERVICE\MSSQLSERVER).
- Update the Microsoft.Data.SqlClient assemblies used by Mashup due to security vulnerability CVE-2022-41064.