Merge pull request #35882 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-19 23:30 UTC

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

docs/database-engine/configure-windows/cross-db-ownership-chaining-server-configuration-option.md

@@ -3,7 +3,7 @@ title: "Server Configuration: cross db ownership chaining"
 description: "Learn how to use the cross db ownership chaining option in SQL Server. View considerations for turning cross-database ownership chaining on and off."
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 08/26/2025
+ms.date: 11/19/2025
 ms.service: sql
 ms.subservice: configuration
 ms.topic: conceptual
@@ -33,7 +33,9 @@ This server option allows you to control cross-database ownership chaining at th
 To determine the current status of cross-database ownership chaining, execute the following query:
 
 ```sql
-SELECT is_db_chaining_on, name FROM sys.databases;
+SELECT is_db_chaining_on,
+       name
+FROM sys.databases;
 ```
 
 A result of `1` indicates that cross-database ownership chaining is enabled.
@@ -50,6 +52,12 @@ Before turning cross-database ownership chaining on or off:
 
 - If you have databases that require cross-database ownership chaining, the recommended practice is to turn off the `cross db ownership chaining` option for the instance using `sp_configure`; then, turn on cross-database ownership chaining for individual databases that require it with the [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql.md) statement.
 
+## Security risk
+
+Enabling cross-database ownership chaining in [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] introduces a potential security vulnerability. When this feature is active, a local database user with elevated privileges can exploit ownership chaining to escalate permissions and potentially gain **sysadmin** access.
+
+You should avoid enabling cross-database ownership chaining at the instance level, and restrict its use to trusted, related databases only.
+
 ## Related content
 
 - [ALTER DATABASE (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql.md)

docs/samples/adventureworks-install-configure.md

@@ -39,7 +39,7 @@ If you're not sure what you need, start with the OLTP version that matches your
 | OLTP | Data Warehouse | Lightweight |
 | --- | --- | --- |
 | [AdventureWorks2025.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorks2025.bak) | [AdventureWorksDW2025.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2025.bak) | [AdventureWorksLT2025.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksLT2025.bak) |
-| [AdventureWorks2025.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorks2025.bak) | [AdventureWorksDW2022.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2022.bak) | [AdventureWorksLT2022.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksLT2022.bak) |
+| [AdventureWorks2022.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorks2022.bak) | [AdventureWorksDW2022.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2022.bak) | [AdventureWorksLT2022.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksLT2022.bak) |
 | [AdventureWorks2019.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorks2019.bak) | [AdventureWorksDW2019.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2019.bak) | [AdventureWorksLT2019.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksLT2019.bak) |
 | [AdventureWorks2017.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorks2017.bak) | [AdventureWorksDW2017.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2017.bak) | [AdventureWorksLT2017.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksLT2017.bak) |
 | [AdventureWorks2016.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorks2016.bak) | [AdventureWorksDW2016.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksDW2016.bak) | [AdventureWorksLT2016.bak](https://github.com/Microsoft/sql-server-samples/releases/download/adventureworks/AdventureWorksLT2016.bak) |

docs/sql-server/azure-arc/media/migrate-to-azure-sql-managed-instance/database-migration-summary.png

@@ -36,6 +36,10 @@ First, you choose an appropriate SQL Managed Instance target and prepare your en
 
 Database migration is available by default for all SQL Server instances enabled by Azure Arc, starting with [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)].
 
+The **Database Migration** pane also has a useful summary of the migration status for your instance, such as the number of total databases, the recommended target, the number of completed migrations, and the number of ongoing migrations: 
+
+:::image type="content" source="media/migrate-to-azure-sql-managed-instance/database-migration-summary.png" alt-text="Screenshot of the summary on the Database Migration pane in the Azure portal." lightbox="media/migrate-to-azure-sql-managed-instance/database-migration-summary.png":::
+
 ## Integrated migration methods
 
 Choose the migration method that best fits your needs on the **Database migration** pane. After an initial configuration to prepare your environment, the migration process automates the rest based on your selection.
@@ -51,7 +55,7 @@ The following table summarizes the two methods built into the migration process:
 | **Description** | Most performant method with near real-time replication. Provides a read-only (R/O) database on the target, so you can query your data in near-real time during the migration to offload R/O workloads on the secondary, or check data during the migration. Best possible minimum downtime migration. | Most compatible migration method. Upload backups to an intermediary Azure blob storage account that the LRS service automatically restores to SQL Managed Instance continuously. No R/O database replica is available on the target. |
 | **Supported versions** | SQL Server 2016 and later on Windows Server 2016 and later | SQL Server 2012 and later on Windows Server 2012 and later |
 | **Supported editions** | Enterprise, Standard, and Developer editions | All editions |
-| **Recommended for** | Business-critical workloads that require minimum downtime during migration and access to a R/O database on the target, with a destination target of either a General Purpose or Business Critical SQL Managed Instance. | General purpose workloads where some planned downtime is acceptable and destination target of a General Purpose SQL Managed Instance. Not recommended for Business Critical SQL managed instance targets. |
+| **Recommended for** | Business-critical workloads that require minimum downtime during migration and access to a read-only database on the target, with a destination target of either a General Purpose or Business Critical SQL Managed Instance. | General purpose workloads where some planned downtime is acceptable and destination target of a General Purpose SQL Managed Instance. Not recommended for Business Critical SQL managed instance targets. |
 
 For an in-depth comparison of the two migration methods, see [Compare Managed Instance link with LRS for migration](/azure/azure-sql/managed-instance/log-replay-service-compare-mi-link).
 
@@ -136,7 +140,7 @@ After your target is ready, start the migration process.
 
 Once you've prepared your environment for [Managed Instance link migration](migration-sql-mi-prepare-link.md), you can migrate your SQL Server databases to Azure SQL Managed Instance. 
 
-Follow these steps to migrate your SQL Server databases to SQL Managed Instance by using the Managed Instance link::
+Follow these steps to migrate your SQL Server databases to SQL Managed Instance by using the Managed Instance link:
 
 1. On the **Database migration** pane, select **Migrate data**.
 1. On the **New data migration** pane, choose **Migrate using real-time replication (online)**:
@@ -173,7 +177,7 @@ Follow these steps to migrate your SQL Server databases to SQL Managed Instance
 
    :::image type="content" source="media/migrate-to-azure-sql-managed-instance/migrate-data-lrs.png" alt-text="Screenshot of the LRS migration option on the Migrate Data page in the Azure portal.":::
 
-1. On the **Select source databases** tab, check the boxes next to the databases that you want to migrate, and then use **Next** to proceed to the next page.:
+1. On the **Select source databases** tab, check the boxes next to the databases that you want to migrate, and then use **Next** to proceed to the next page:
 
    :::image type="content" source="media/migrate-to-azure-sql-managed-instance/select-source-database-lrs.png" alt-text="Screenshot of the select source databases page when you migrate your database with LRS in the Azure portal." lightbox="media/migrate-to-azure-sql-managed-instance/select-source-database-lrs.png":::
 
@@ -197,7 +201,7 @@ The **Monitor and cutover** pane shows useful information about the migration pr
 
 :::image type="content" source="media/migrate-to-azure-sql-managed-instance/monitor-migration.png" alt-text="Screenshot of the monitor migration page in the Azure portal." lightbox="media/migrate-to-azure-sql-managed-instance/monitor-migration.png":::
 
-You can pause, resume, or cancel the migration from the **Monitor and cutover** pane. You can also view logs for information about the migration. Selecting a database takes you to a pane with more details about the source and target.
+You can complete or cancel the migration from the **Monitor and cutover** pane. You can also view logs for information about the migration. Selecting a database takes you to a pane with more details about the source and target.
 
 After the migration finishes, the migration status shows **Ready for cutover**. To cut over to the SQL Managed Instance target, select **Cutover** on the **Monitor and cutover** pane. You can also use the database details pane.
 

docs/sql-server/azure-arc/media/migrate-to-azure-sql-managed-instance/lrs-migration-method.png

@@ -5,15 +5,15 @@ description: Learn about the capabilities of SQL Server migration in Azure Arc.
 author: ajithkr-ms
 ms.author: ajithkr
 ms.reviewer: mikeray, mathoma
-ms.date: 11/18/2025
+ms.date: 11/19/2025
 ms.topic: how-to
 ---
 
 # SQL Server migration in Azure Arc Overview
 
 [!INCLUDE [sqlserver](../../includes/applies-to-version/sqlserver.md)]
 
-This article provides an overview of SQL Server migration in Azure Arc for [SQL Server instances enabled by Azure Arc](overview.md). 
+This article provides an overview of SQL Server migration in Azure Arc for [SQL Server enabled by Azure Arc](overview.md).
 
 ## Overview
 
@@ -31,7 +31,7 @@ SQL Server migration in Azure Arc is available by default for all SQL Server ins
 
 ## Migration targets
 
-Currently, you can only migrate to [Azure SQL Managed Instance](migrate-to-azure-sql-managed-instance.md). 
+Currently, you can only migrate to [Migration to Azure SQL Managed Instance - SQL Server migration in Azure Arc](migrate-to-azure-sql-managed-instance.md).
 
 ## Microsoft Copilot assisted migration
 
@@ -93,11 +93,23 @@ You can obtain a migration assessment for SQL Servers located anywhere, such as:
 
 The assessment is available for any instance of SQL Server enabled by Azure Arc.
 
+## Database migration
+
+On the **Database migration** pane, you can migrate your SQL Server databases to Azure SQL Managed Instance. The migration process is fully managed and automated from the Azure portal. Once you're ready to start, you can use the tiles to assess your SQL Server databases, choose a migration target, and start the migration process.
+
+**Database migration** guides you through the migration with easy to follow tiles for each step of the process:
+
+:::image type="content" source="media/migrate-to-azure-sql-managed-instance/migration-home-page.png" alt-text="Screenshot that shows the migration home page for a SQL Server instance in the Azure portal." lightbox="media/migrate-to-azure-sql-managed-instance/migration-home-page.png":::
+
+The **Database Migration** pane also has a useful summary of the migration status for your instance, such as the number of total databases, the recommended target, the number of completed migrations, and the number of ongoing migrations:
+
+:::image type="content" source="media/migrate-to-azure-sql-managed-instance/database-migration-summary.png" alt-text="Screenshot of the summary on the Database Migration pane in the Azure portal." lightbox="media/migrate-to-azure-sql-managed-instance/database-migration-summary.png":::
+
 ## Related content
 
-- [Migration dashboard](migration-inventory.md)
-- [Assessment for migration to Azure](migration-assessment.md)
-- [Prepare environment for a Managed Instance link migration](migration-sql-mi-prepare-link.md)
-- [Prepare environment for an LRS migration](migration-sql-mi-prepare-log-replay-service.md)
+- [Track migration journey by using migration dashboard - SQL Server enabled by Azure Arc](migration-inventory.md)
+- [Assess migration readiness - SQL Server enabled by Azure Arc](migration-assessment.md)
+- [Prepare environment for a Managed Instance link migration - SQL Server migration in Azure Arc](migration-sql-mi-prepare-link.md)
+- [Prepare environment for LRS migration - SQL Server migration in Azure Arc](migration-sql-mi-prepare-log-replay-service.md)
 - [SQL Server enabled by Azure Arc](overview.md)
 - [Deployment options for SQL Server enabled by Azure Arc](deployment-options.md)