Merge pull request #36527 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-29 18:30 UTC

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

azure-sql/includes/virtual-machines-best-practices-vm-size.md

@@ -2,14 +2,14 @@
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 06/16/2025
+ms.date: 01/23/2026
 ms.service: virtual-machines
 ms.topic: include
 ms.custom:
   - ignite-2024
 ---
 - Identify workload performance characteristics to determine the appropriate VM size for your business.
-- If you're migrating to Azure, use the [Azure SQL migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) to find the right VM size for your existing SQL Server workload, and then migrate with [Azure Data Studio](/azure/dms/tutorial-sql-server-to-virtual-machine-online-ads). 
+- If you're migrating to Azure, [assess migration readiness](/sql/sql-server/azure-arc/migration-assessment) to find the right VM size for your existing SQL Server workload, and then migrate with [Azure Database Migration Service](/azure/dms/dms-overview). 
 - Use Azure Marketplace images to deploy your SQL Server VMs as the SQL Server settings and storage options are configured for optimal performance.
 - Use VM sizes with 4 or more vCPUs.
 - Use memory optimized virtual machine sizes for the best performance of SQL Server workloads. 

azure-sql/managed-instance/managed-instance-link-best-practices.md

@@ -5,7 +5,7 @@ description: This article describes the Managed Instance link, which you can use
 author: djordje-jeremic
 ms.author: djjeremi
 ms.reviewer: mathoma, randolphwest
-ms.date: 11/18/2025
+ms.date: 01/28/2026
 ms.service: azure-sql-managed-instance
 ms.subservice: data-movement
 ms.topic: concept-article
@@ -32,7 +32,7 @@ Though the link supports replication of one database per link, you can replicate
 The link feature currently offers the following functionality:
 
 - **One-way replication from SQL Server versions 2016, 2017 and 2019**: Use the link feature to replicate data one way from SQL instance to Azure SQL Managed Instance. Although you can manually fail over to your managed instance if there's a disaster, doing so breaks the link, and failing back isn't supported. 
-- **Disaster recovery (SQL Server 2022)**: Use the link feature to replicate data between SQL Server 2022 and SQL Managed Instance, manually fail over to your secondary during a disaster, and fail back to your primary after you mitigate the disaster. Either SQL Server or SQL Managed Instance can be the initial primary. 
+- **Disaster recovery (SQL Server 2022 and SQL Server 2025)**: Use the link feature to replicate data between SQL Server 2022 or SQL Server 2025 and SQL Managed Instance, manually fail over to your secondary during a disaster, and fail back to your primary after you mitigate the disaster. Either SQL Server or SQL Managed Instance can be the initial primary. 
 
 You can keep running the link for as long as you need it, for months and even years at a time. And for your modernization journey, if or when you're ready to migrate to Azure, the link enables a considerably improved migration experience. Migration through the link offers minimal downtime compared to all other available migrations options, providing a true online migration to your SQL Managed Instance.
 
@@ -61,8 +61,8 @@ The following table lists the functionality of the link feature and the minimum
 | Azure SQL Managed Instance |  [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) for the secondary SQL Server instance replica |  [Bi-directional](#disaster-recovery) | Configuring a link *from* Azure SQL Managed Instance to, and bidirectional failover with, is supported by:  <br /> - SQL Server 2025 and SQL MI with the [**SQL Server 2025 update policy**](update-policy.md#sql-server-2025-update-policy) <br /> - SQL Server 2022 and SQL MI with the [**SQL Server 2022 update policy**](update-policy.md#sql-server-2022-update-policy)  | 
 | SQL Server 2025 (17.x) | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) |  [Bi-directional](#disaster-recovery)|  [SQL Server 2025 RTM (17.0.1000.7)](/sql/sql-server/sql-server-2025-release-notes) |
 | SQL Server 2022 (16.x) | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) |  [Bi-directional](#disaster-recovery) |  - [SQL Server 2022 RTM (16.0.1000.6)](/sql/sql-server/sql-server-2022-release-notes): Creating a link *from* SQL Server 2022 to SQL MI <br /> -  [SQL Server 2022 CU10 (16.0.4095.4)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate10): Creating a link *from* SQL MI to SQL Server 2022<sup>1</sup> <br /> - [SQL Server 2022 CU13 (16.0.4125.3)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate13): Failing over the link using [Transact-SQL](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database) | 
-| SQL Server 2019 (15.x) | [Windows Server only](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019) | From SQL Server to SQL MI only | [SQL Server 2019 CU20 (15.0.4312.2)](https://support.microsoft.com/topic/kb5024276-cumulative-update-20-for-sql-server-2019-4b282be9-b559-46ac-9b6a-badbd44785d2) |
-| SQL Server 2017 (14.x) | [Windows Server only](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server#operating-system-support-for-sql-server-2017) | From SQL Server to SQL MI only | [SQL Server 2017 CU31 (14.0.3456.2)](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate31) and the matching [SQL Server 2017 Azure Connect pack (14.0.3490.10)](/troubleshoot/sql/releases/sqlserver-2017/azureconnect) | 
+| SQL Server 2019 (15.x) | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) | From SQL Server to SQL MI only | [SQL Server 2019 CU20 (15.0.4312.2)](https://support.microsoft.com/topic/kb5024276-cumulative-update-20-for-sql-server-2019-4b282be9-b559-46ac-9b6a-badbd44785d2) |
+| SQL Server 2017 (14.x) | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server#operating-system-support-for-sql-server-2017) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) | From SQL Server to SQL MI only | [SQL Server 2017 CU31 (14.0.3456.2)](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate31) and the matching [SQL Server 2017 Azure Connect pack (14.0.3490.10)](/troubleshoot/sql/releases/sqlserver-2017/azureconnect) | 
 | SQL Server 2016 (13.x) | [Windows Server only](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server#operating-system-support-for-sql-server-2017) | From SQL Server to SQL MI only| [SQL Server 2016 SP3 (13.0.6300.2)](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-cumulative-update-cu-builds) and the matching [SQL Server 2016 Azure Connect pack (13.0.7000.253)](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-azure-connect-pack-builds) |
 | SQL Server 2014 (12.x) and earlier | N/A | N/A | Versions before SQL Server 2016 aren't supported.|
 

azure-sql/managed-instance/managed-instance-link-feature-overview.md

@@ -57,7 +57,7 @@ To check the link state in SSMS, follow these steps:
 
 ### [Transact-SQL (T-SQL)](#tab/tsql)
 
-Use T-SQL to determine the state of the link during the seeding phase, or after data synchronization begins. 
+Use T-SQL to determine the state of the link during the seeding phase, or after data synchronization begins. The [sys.dm_hadr_physical_seeding_stats](/sql/relational-databases/system-dynamic-management-views/sys-dm-hadr-physical-seeding-stats) DMV can be used to track the initial seeding status. The `estimate_time_complete_utc` column is based on the current `transfer_rate_bytes_per_second` and uncompressed remaining data size (when `is_compression_enabled` = 0). For Managed Instance link, data compression is used, so `estimate_time_complete_utc` is expected to be an overestimate.
 
 Use the following T-SQL query to determine the status of the link during the seeding phase on the SQL Server or SQL Managed Instance that hosts the database seeded through the link: 
 
@@ -179,9 +179,6 @@ The following errors can occur when creating a link (Link state: `LinkCreationEr
    To resolve this issue, you must [drop](managed-instance-link-configure-how-to-ssms.md#drop-a-link) and recreate the link.   
    To avoid this issue, pause transaction log backups on SQL Server for database being replicated during the initial seeding phase.
 
-
-
-
 ## Inconsistent state after forced failover
 
 Following a forced [failover](managed-instance-link-failover-how-to.md), you might encounter a split-brain scenario where both replicas are in the primary role, leaving the link in an inconsistent state. This can happen if you fail over to the secondary replica during a disaster, and then the primary replica comes back online.
@@ -239,7 +236,6 @@ It's possible for the certificate used for the link to expire. If the certificat
 
 [!INCLUDE [azure-sql-managed-instance-link-check-network](../includes/sql-managed-instance/azure-sql-managed-instance-link-check-network.md)]
 
-
 ## Related content
 
 For more information on the link feature, review the following resources:

azure-sql/managed-instance/managed-instance-link-troubleshoot-how-to.md

@@ -4,7 +4,7 @@ description: An overview of the contained availability group feature of Always O
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 01/14/2026
+ms.date: 01/27/2026
 ms.service: sql
 ms.subservice: high-availability
 ms.topic: overview
@@ -151,8 +151,6 @@ If you use a network resource for the backup location, all servers that host rep
 
 **Applies to**: [!INCLUDE [sssql25-md](../../../includes/sssql25-md.md)] CU 1 and later versions.
 
-[!INCLUDE [sql-server-2025-cu-1-removed](../../../linux/includes/sql-server-2025-cu-1-removed.md)]
-
 In [!INCLUDE [sssql25-md](../../../includes/sssql25-md.md)] Cumulative Update (CU) 1, you can enable database creation and restoration directly within a contained availability group session, through the contained AG listener. This enhancement streamlines workflows for users assigned the appropriate roles, allowing seamless operations within contained AG environments.
 
 Only users with the **dbcreator** role can create databases in a contained AG session. Only users with the **db_owner** or **sysadmin** role can restore databases.

docs/database-engine/availability-groups/windows/contained-availability-groups-overview.md

@@ -0,0 +1,11 @@
+---
+author: rwestMSFT
+ms.author: randolphwest
+ms.date: 01/28/2026
+ms.service: sql
+ms.topic: include
+ms.custom:
+  - linux-related-content
+---
+
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server 2022](_ss2022.md)] and later versions on Linux

docs/includes/applies-to-version/sqlserver2022-and-later-linux.md

@@ -0,0 +1,10 @@
+---
+author: dimitri-furman
+ms.author: dfurman
+ms.date: 01/27/2025
+ms.service: sql
+ms.topic: include
+ms.custom:
+  - build-2025
+---
+Azure SQL Managed Instance<sup>[2025](/azure/azure-sql/managed-instance/update-policy#sql-server-2025-update-policy)</sup>

docs/includes/applies-to-version/ssazure-sqlmi-2025.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 11/18/2025
+ms.date: 01/27/2026
 ms.service: sql
 ms.topic: include
 ms.custom:
@@ -11,9 +11,9 @@ ms.custom:
 | --- | --- |
 | `Evaluation` | SQL Server Evaluation edition |
 | `Express` | SQL Server Express edition |
-| `StandardDeveloper`<br /><br />(For containers, use `DeveloperStandard`) | SQL Server Standard Developer edition |
+| `StandardDeveloper` | SQL Server Standard Developer edition |
 | `Standard` | SQL Server Standard edition |
-| `EnterpriseDeveloper`<br /><br />(For containers, use `Developer`) | SQL Server Enterprise Developer edition |
+| `EnterpriseDeveloper` | SQL Server Enterprise Developer edition |
 | `Enterprise` | This legacy option represents Enterprise edition Server + Client Access License (CAL) based licensing, and is limited to a maximum of 20 cores per SQL Server instance. `Enterprise` isn't available for new agreements. You should choose `EnterpriseCore` when you wish to deploy Enterprise edition. |
 | `EnterpriseCore` | SQL Server Enterprise Core edition. `EnterpriseCore` represents the core-based server licensing model with no core limits. For more information, see [Compute capacity limits by edition of SQL Server](../../sql-server/compute-capacity-limits-by-edition-of-sql-server.md). |
 | `A product key` | If you specify a product key, it must be in the form of `#####-#####-#####-#####-#####`, where `#` is a number or a letter. |