Merge pull request #36093 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-16 23:30 UTC

Author: learn-build-service-prod[bot]

azure-sql/database/serverless-tier-overview.md

@@ -4,7 +4,7 @@ description: This article describes the new serverless compute tier and compares
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: moslake, mathoma, dfurman, blakhani
-ms.date: 12/15/2025
+ms.date: 12/16/2025
 ms.service: azure-sql-database
 ms.subservice: service-overview
 ms.topic: conceptual
@@ -207,9 +207,9 @@ Auto-resuming is triggered if any of the following conditions are true at any ti
 
 Monitoring, management, or other solutions performing any of these operations trigger auto-resuming. Auto-resuming is also triggered during the deployment of some service updates that require the database be online.
 
-#### Auto-resume trigger indentification
+#### Auto-resume trigger identification
 
-Auto-resume triggers are exposed in the Azure Monitor activity log for **Resume Databases** operations under the `Caller` property in the JSON of the **Succeeded** event.
+Auto-resume triggers are exposed in the [Azure Monitor activity log](/azure/azure-monitor/platform/activity-log?tabs=log-analytics) for **Resume Databases** operations under the `Caller` property in the JSON of the **Succeeded** event.
 
 ### Connectivity
 

azure-sql/managed-instance/failover-group-configure-sql-mi.md

@@ -478,7 +478,7 @@ To avoid problems from a lower service tier or under-resourced geo-secondary get
 - You can scale the primary and secondary instance up or down to a different compute size within the same service tier or to a different service tier. 
 - When scaling up within the same service tier, scale up the geo-secondary first, and then scale up the primary.
 - When scaling down within the same service tier, reverse the order: scale down the primary first, and then scale down the secondary. 
-- Follow the same sequence when you change the configuration of your instance. If you're scaling resources up, do so on the secondary first. If you're scaling down, do so the primary first. This applies to the following instance configuration changes: 
+- Follow the same sequence when you change the configuration of your instance. If you're scaling resources up, do so on the secondary first. If you're scaling down, do so on the primary first. This applies to the following instance configuration changes: 
   - Upgrading or downgrading the service tier. 
   - Changing the number of vCores.
   - Scaling the storage size.

azure-sql/managed-instance/managed-instance-link-migrate.md

@@ -88,11 +88,14 @@ After you've cut over to the SQL managed instance target, monitor your applicati
 
 For details, review [post-migration](../migration-guides/managed-instance/sql-server-to-managed-instance-guide.md#post-migration). 
 
-## Reverse migrate (SQL Server 2022)
+## Reverse a migration
 
-Starting with SQL Server 2022 CU10, you can configure a link with Azure SQL Managed Instance as the initial primary and SQL Server as the secondary. This capability allows you to reverse migrate from Azure SQL Managed Instance to SQL Server 2022.
+Reverse migration back to SQL Server from Azure SQL Managed Instance might be supported depending on the [update policy](/azure/azure-sql/managed-instance/update-policy) of your SQL managed instance. For example: 
+- [SQL Server 2022 update policy](/azure/azure-sql/managed-instance/update-policy#sql-server-2022-update-policy): Databases from instances configured with the **SQL Server 2022** update policy can be restored back to SQL Server 2022 instances.
+- [SQL Server 2025 update policy](/azure/azure-sql/managed-instance/update-policy#sql-server-2025-update-policy): Databases from instances configured with the **SQL Server 2025** update policy can be restored back to SQL Server 2025 instances.
+- [Always-up-to-date update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy): Databases from instances configured with the **Always-up-to-date** update policy can't be restored back to SQL Server.
 
-To reverse a migration, follow the same steps to configure the link, but start the process with the SQL Managed Instance as your migration source, and the SQL Server 2022 instance as the migration target. 
+If your source SQL Server version is earlier than SQL Server 2022, reverse migration isn't possible. When your database is migrated to SQL Managed Instance, it undergoes an internal upgrade to a newer database version that isn't compatible with earlier SQL Server versions. Reverse migration database compatibility is only available when SQL Managed instance is configured with the corresponding update policy.
 
 ## Related content
 

docs/connect/odbc/bug-fixes.md

@@ -3,17 +3,21 @@ title: List of bugs fixed
 description: This page contains a listing of bugs fixed in each release, starting with Microsoft ODBC Driver 17 for SQL Server.
 author: David-Engel
 ms.author: davidengel
-ms.date: 03/17/2025
+ms.date: 12/17/2025
 ms.service: sql
 ms.subservice: connectivity
-ms.topic: conceptual
+ms.topic: release-notes
 helpviewer_keywords:
   - "driver"
 ---
 # List of bugs fixed
 
 This page contains a listing of bugs fixed in each release, starting with [!INCLUDE[msCoName](../../includes/msconame-md.md)] ODBC Driver 17 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
 
+### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] ODBC Driver 18.6.1.1 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
+
+- Fix TDS packet size in BID trace
+
 ### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] ODBC Driver 18.5.1.1 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
 
 - Fix connection recovery to obtain the active primary node when a server moves
@@ -77,7 +81,7 @@ This page contains a listing of bugs fixed in each release, starting with [!INCL
 ### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] ODBC Driver 18.2 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
 
 - Fix VBS-NONE enclave attestation protocol
-- Fix error when retrieving numeric column with Regional=Yes
+- Fix an error when retrieving numeric column with Regional=Yes
 - Fix intermittent lack of error when server is stopped during bcp out operation
 - Fix error when stored procedure call contains unquoted string parameter
 - Fix a memory leak upon reconnect
@@ -106,7 +110,7 @@ This page contains a listing of bugs fixed in each release, starting with [!INCL
 ### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] ODBC Driver 18.0 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
 
 - Fix UI issues where text was cut off and position of items was off.
-- Fix issue with Active Directory Interactive login where attempting to log in after closing the window of the first failure would automatically succeed if cached credentials were available.
+- Fix issue with Active Directory Interactive login where attempting to sign in after closing the window of the first failure would automatically succeed if cached credentials were available.
 - Fix use of XADTC with Azure SQL Managed Instance.
 - Fix loss of Microsoft Entra authentication mode when reconnecting an idle connection.
 - Fix an issue with federated authentication when using PingFed.
@@ -128,7 +132,7 @@ This page contains a listing of bugs fixed in each release, starting with [!INCL
 ### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame-md.md)] ODBC Driver 17.9 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
 
 - Fix UI issues where text was cut off and position of items was off.
-- Fix issue with Active Directory Interactive login where attempting to log in after closing the window of the first failure would automatically succeed if cached credentials were available.
+- Fix issue with Active Directory Interactive login where attempting to sign in after closing the window of the first failure would automatically succeed if cached credentials were available.
 - Fix use of XADTC with Azure SQL Managed Instance.
 - Fix loss of Microsoft Entra authentication mode when reconnecting an idle connection.
 - Fix an issue with federated authentication when using PingFed.
@@ -213,7 +217,7 @@ This page contains a listing of bugs fixed in each release, starting with [!INCL
 - Fixed detection of connection liveness
 - Fixed incorrect detection of closed sockets
 - Fixed an infinite wait when attempting to release a statement handle during failed recovery
-- Fixed incorrect uninstallation behavior when both version 13 and 17 are installed on Windows
+- Fixed incorrect uninstallation behavior when both versions 13 and 17 are installed on Windows
 - Fixed decryption behavior on older Windows platform (Windows 7, 8 and Server 2012)
 - Fixed a cache issue when using ADAL Authentication on Windows
 - Fixed an issue that was locking and overwriting trace logs on Windows