release-2022-cu-16 -> main -- 10:30 AM PST (#32399)

* Add trace flag 8531 for bug 3417400 of SQL Server 2022 CU16

* Add the information of SQL Server 2022 CU16 for bug 3419788

* CU 16 errors and events

---------

Co-authored-by: Simonx Xu <v-six@microsoft.com>
Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Alma Jenks <v-alje@microsoft.com>
Co-authored-by: Mark Ghanayem <22989000+markingmyname@users.noreply.github.com>

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-14000-14999.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 03/14/2024
+ms.date: 11/14/2024
 ms.topic: include
 ---
 | Error | Severity | Event logged | Description |
@@ -80,6 +80,7 @@ ms.topic: include
 | 14076 | 16 | No | Could not grant replication login permission to '%s'. |
 | 14077 | 10 | No | The publication was updated successfully. |
 | 14078 | 16 | No | The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', 'enabled_for_internet', 'allow_push', 'allow_pull', 'allow_anonymous', or 'retention'. |
+| 14079 | 16 | No | Object '%ls' cannot be published because it was created by an internal SQL Server component. |
 | 14080 | 16 | No | The remote server "%s" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers. |
 | 14085 | 16 | No | The Subscriber information could not be obtained from the Distributor. |
 | 14088 | 16 | No | The table '%s' must have a primary key to be published using the transaction-based method. |
@@ -120,6 +121,8 @@ ms.topic: include
 | 14126 | 16 | No | You do not have the required permissions to complete the operation. |
 | 14128 | 16 | No | Invalid @subscription_type parameter value. Valid options are 'push' or 'pull'. |
 | 14129 | 16 | No | The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication. |
+| 14130 | 10 | No | WARNING: The database '%s' does not contain database master key. Create a database master key and then update all replication secrets in this database. |
+| 14131 | 16 | No | The database '%s' does not contain database master key. Create database master key and repeat the procedure. |
 | 14135 | 16 | No | There is no subscription on Publisher '%s', publisher database '%s', publication '%s'. |
 | 14136 | 16 | No | The keyword 'all' is reserved by replication stored procedures. |
 | 14137 | 16 | No | The @value parameter value must be either 'true' or 'false'. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-19000-20999.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 09/12/2024
+ms.date: 11/14/2024
 ms.topic: include
 ---
 | Error | Severity | Event logged | Description |
@@ -263,6 +263,7 @@ ms.topic: include
 | 19529 | 16 | No | Failed to create a database backup on secondary replica for database "%ls". The checkpoint LSN from primary replica could not be redone. Check the health of the database in the SQL Server error log on both primary and secondary replica. If the database is healthy, try the operation again. |
 | 19530 | 16 | No | The %ls operation is not allowed by the current availability group configuration. The required_synchronized_secondaries_to_commit needs to be 0 when changing availability mode to ASYNCHRONOUS_COMMIT. Change required_synchronized_secondaries_to_commit to 0 and retry the operation. |
 | 19533 | 16 | No | Cannot create distributed availability group '%.\*ls' as it requires two Availaiblity Group Replicas, however %d were specified. |
+| 19536 | 10 | No | The default startup routine of database '%.\*ls' that belongs to an availability group (Group ID: %d) cannot be skipped because SQL Server did not initialize the Availability Replica Manager. This is an informational message only. No user action is required. |
 | 19601 | 16 | No | System error. |
 | 19602 | 16 | No | System error. |
 | 19603 | 16 | No | System error. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-31000-41399.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/10/2024
+ms.date: 11/14/2024
 ms.topic: include
 ---
 > [!NOTE]
@@ -1252,6 +1252,16 @@ ms.topic: include
 | 37559 | 16 | No | Object_id is not a valid option |
 | 37563 | 16 | Yes | The primary managed identity is not selected for this server. Enable the primary managed identity for Microsoft Entra authentication for this server. For more information see (https://aka.ms/sql-server-managed-identity-doc). |
 | 37564 | 10 | Yes | The managed identity with Client_ID/Application_ID '%ls', is the primary identity assigned for this server. |
+| 37566 | 16 | No | Operations on customer managed key '%s' are not allowed because the key has been disabled in Azure Key Vault '%s'. Please enable the key. For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37567 | 16 | No | Operations on customer managed key '%s' are not allowed in Azure Key Vault '%s'. Please allow the following operations on the key: "get", "wrapKey", "unwrapKey". For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37568 | 16 | No | One of required operations on customer managed key '%s' is not allowed for currently chosen RBAC role of the managed instance '%s' identity on Azure Key Vault '%s'. Please change to a RBAC role permitting the following permissions on the key vault: "get", "wrapKey", "unwrapKey". For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting |
+| 37569 | 16 | No | Connection to Azure Key Vault '%s' was forbidden by Azure Key Vault firewall policy. Please review the Azure Key Vault firewall policy to enable connections from Managed Instance '%s'. For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37570 | 16 | No | One of required operations on customer managed key '%s' on Azure Key Vault '%s' is not allowed for currently set key vault policy used by managed instance '%s' identity. Please use a policy permitting the following permissions on the key vault: "get", "wrapKey", "unwrapKey". For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37571 | 16 | No | Azure Key Vault '%s' operation requested by Managed Instance '%s' failed due to insufficient permissions (inner error code: '%s'). For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37572 | 16 | No | Customer managed key '%s' was not found in Azure Key Vault '%s'. If it was recently deleted, recovery could be possible if 'soft-delete' protection is enabled on the key vault. For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37573 | 16 | No | Connection to Azure Key Vault '%s' could not be established. Please review network settings for Managed Instance '%s'. For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37574 | 16 | No | Azure Key Vault URI '%s' could not be resolved. Please ensure the key vault URI is valid and that your network settings for Managed Instance '%s' are not blocking access to Azure Public DNS. For help resolving this issue, please see https://aka.ms/sqlmi-tde-troubleshooting. |
+| 37576 | 16 | No | The current SQL Server Connector version for Microsoft Azure Key Vault does not support the managed identity (see https://aka.ms/sql-server-managed-identity-doc). Upgrade the SQL Server Connector to its latest version (see https://www.microsoft.com/en-us/download/details.aspx?id=45344&msockid=2aa7acc4c900647e098ebfb5c8ba6506). |
 | 38001 | 16 | No | Cannot find the file id %d in the database '%s'. |
 | 38002 | 16 | No | Only users having %s permission can execute this stored procedure. |
 | 39001 | 16 | No | Only SELECT statement is supported for input data query to 'sp_execute_external_script' stored procedure. |

docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-7000-7999.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 01/11/2024
+ms.date: 11/14/2024
 ms.topic: include
 ---
 | Error | Severity | Event logged | Description |
@@ -177,6 +177,7 @@ ms.topic: include
 | 7448 | 16 | Yes | Linked Server login mapping with "useself" property set is not allowed when using AAD '%ls' authentication mode. |
 | 7449 | 16 | Yes | Linked Server User-assigned MSI mode AAD authentication functionality is not supported on the service side. Use system-assigned identity instead. |
 | 7450 | 16 | Yes | Querying linked server '%ls' failed. Either login for Linked Server AAD '%ls' authentication mode does not exist or login's 'useself' attribute is set to true. |
+| 7455 | 16 | Yes | Service Master Key is not generated or access is lost so encryption/decryption of linked server passwords cannot be done. |
 | 7601 | 16 | No | Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.\*ls' because it is not full-text indexed. |
 | 7602 | 16 | No | The full-text service (msftesql%ls%ls) is not available. The system administrator must start this service. |
 | 7603 | 10 | No | Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%d', database ID '%d' is reset. |

docs/relational-databases/replication/agents/replication-distribution-agent.md

@@ -346,7 +346,7 @@ In [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] CU 22 and later vers
 
 Before [!INCLUDE [sssql17-md](../../../includes/sssql17-md.md)] CU 22, `UseOledbStreaming` writes to the `C:\Program Files\Microsoft SQL Server\<version>\COM` folder.
 
-In [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] CU 29, you can disable OLE DB streaming by updating `-UseOledbStreaming` to `0` to avoid the error mentioned in [Error message when you run the Distribution Agent in SQL Server]( /troubleshoot/sql/database-engine/replication/error-run-distribution-agent).
+In [!INCLUDE [sssql19-md](../../../includes/sssql19-md.md)] CU 29, [!INCLUDE [ssSQL22](../../../includes/sssql22-md.md)] CU 16, and later versions, you can disable OLE DB streaming by updating `-UseOledbStreaming` to `0` to avoid the error mentioned in [Error message when you run the Distribution Agent in SQL Server]( /troubleshoot/sql/database-engine/replication/error-run-distribution-agent).
 
 ## Remarks
 

docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md

@@ -4,7 +4,7 @@ description: "Learn how to set specific server characteristics or to alter a par
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: wiassaf
-ms.date: 09/25/2024
+ms.date: 11/01/2024
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: "language-reference"
@@ -223,7 +223,7 @@ Trace flag behavior might not be supported in future releases of [!INCLUDE [ssNo
 | <a id="tf8286"></a>**8286** | Forces the cleanup query to use the `FORCE ORDER` hint to improve performance. Can be used with [TF 8287](#tf8287) to use the `FORCESEEK` hint. For more information, see [KB5022375](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate1).<br /><br />**Applies to:** [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] CU 19, [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 1, and later versions.<br /><br />**Scope:** Global only. |
 | <a id="tf8287"></a>**8287** | Forces the cleanup query to use the `FORCESEEK` hint to improve performance. Can be used with [TF 8286](#tf8286) to use the `FORCE ORDER` hint. For more information, see [KB5022375](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate1).<br /><br />**Applies to:** [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] CU 19, [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 1, and later versions.<br /><br />**Scope:** Global only. |
 | <a id="tf8290"></a>**8290** | After this trace flag is enabled, the change tracking (CT) auto cleanup process will reset any invalid cleanup version to a cleanup version based on the retention period. After you enable this trace flag, you must let the auto cleanup process run. For more information, see [KB4538365](https://support.microsoft.com/kb/4538365).<br /><br />**Applies to:** [!INCLUDE [ssSQL17](../../includes/sssql17-md.md)] CU 19, [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] CU 4, [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], and later versions.<br /><br />**Scope:** Global or session. |
-| <a id="tf8531"></a>**8531** | Enables the fix for a contention issue with high `KTM_RECOVERY_MANAGER` wait times that you might encounter when running XA distributed transactions.<br /><br />**Applies to:** [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] CU 29 and later versions.<br /><br />**Scope:** Global and startup only. |
+| <a id="tf8531"></a>**8531** | Enables the fix for a contention issue with high `KTM_RECOVERY_MANAGER` wait times that you might encounter when running XA distributed transactions.<br /><br />**Applies to:** [!INCLUDE [sql-server-2019](../../includes/sssql19-md.md)] CU 29, [!INCLUDE [ssSQL22](../../includes/sssql22-md.md)] CU 16, and later versions.<br /><br />**Scope:** Global and startup only. |
 | <a id="tf8558"></a>**8558** | Enables a fix to ensure that you don't observe edge cases where when RCSI isolation level is enabled then a transaction sometimes can't see the latest data from the tables that were modified using DTC transactions even after xa_commit returned success for a short duration of time.<br /><br />**Note:** Ensure that you thoroughly test this option, before rolling it into a production environment.<br /><br />**Applies to:** [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] CU 18, [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], and later versions.<br /><br />**Scope:** Global only. |
 | <a id="tf8721"></a>**8721** | Reports to the error log when autoupdate statistics executes. For more information, see an archived version of [KB195565](https://mskb.pkisolutions.com/kb/195565).<br /><br />**Note:** This trace flag requires Trace Flag [3605](#tf3605) to be enabled.<br /><br />**Scope:** Global only. |
 | <a id="tf8744"></a>**8744** | Disable prefetching for the [Nested Loops](../../relational-databases/performance/joins.md#nested_loops) operator.<br /><br />**Warning:** Incorrect use of this trace flag might cause additional physical reads when [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] executes plans that contain the Nested Loops operator.<br /><br />**Scope:** Global and session. |