Merge pull request #33743 from MicrosoftDocs/main

4/7/2025 PM Publish

Author: Albertyang0

data-migration/sql-server/database/overview.md

@@ -92,7 +92,7 @@ We recommend the following migration tools:
 | Technology | Description |
 | --- | --- |
 | [Azure Migrate](/azure/migrate/how-to-create-azure-sql-assessment) | This Azure service helps you discover and assess your SQL data estate at scale on VMware. It provides Azure SQL deployment recommendations, target sizing, and monthly estimates. |
-| [Azure SQL migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) | Powered by the [Azure Database Migration Service](/azure/dms/dms-overview), the Azure SQL Migration extension for Azure Data Studio helps you to assess your database requirements to understand your migration readiness, get the right-sized SKU recommendations for Azure resources, and migrate your SQL Server database to Azure. You can migrate single databases or at scale using [PowerShell and Azure CLI](/azure/dms/migration-dms-powershell-cli). |
+| [Azure Database Migration Service](/data-migration/sql-server/database/database-migration-service?toc=%2Fazure%2Fdms%2Ftoc.json&tabs=azure-data-studio) | Azure Database Migration Service is a fully managed service designed to enable seamless migrations from multiple database sources to Azure data platforms with minimal downtime. |
 
 The following table lists alternative migration tools:
 
@@ -102,6 +102,8 @@ The following table lists alternative migration tools:
 | [Import Export Service/BACPAC](/azure/azure-sql/database/database-import) | [BACPAC](/sql/relational-databases/data-tier-applications/data-tier-applications#bacpac) is a Windows file with a .bacpac extension that encapsulates a database's schema and data. You can use BACPAC to both export data from a SQL Server source and import the data into Azure SQL Database. A BACPAC file can be imported to a new SQL database through the Azure portal.<br /><br />For scale and performance with large databases sizes or a large number of databases, consider using the [SqlPackage](/azure/azure-sql/database/database-import#use-sqlpackage) command-line tool to export and import databases. |
 | [Bulk copy](/sql/relational-databases/import-export/import-and-export-bulk-data-by-using-the-bcp-utility-sql-server) | The [bulk copy program (bcp) tool](/sql/tools/bcp-utility) copies data from an instance of SQL Server into a data file. Use the tool to export the data from your source and import the data file into the target SQL database.<br /><br />For high-speed bulk copy operations to move data to Azure SQL Database, you can use the [Smart Bulk Copy tool](/samples/azure-samples/smartbulkcopy/smart-bulk-copy/) to maximize transfer speed by taking advantage of parallel copy tasks. |
 | [Azure Data Factory](/azure/data-factory/connector-azure-sql-database) | The [Copy activity](/azure/data-factory/copy-activity-overview) in Azure Data Factory migrates data from source SQL Server databases to Azure SQL Database by using built-in connectors and an [integration runtime](/azure/data-factory/concepts-integration-runtime).<br /><br />Data Factory supports a wide range of [connectors](/azure/data-factory/connector-overview) to move data from SQL Server sources to Azure SQL Database. |
+| [Azure SQL migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) | Powered by the [Azure Database Migration Service](/azure/dms/dms-overview), the Azure SQL Migration extension for Azure Data Studio helps you to assess your database requirements to understand your migration readiness, get the right-sized SKU recommendations for Azure resources, and migrate your SQL Server database to Azure. You can migrate single databases or at scale using [PowerShell and Azure CLI](/azure/dms/migration-dms-powershell-cli). |
+
 
 ## Compare migration options
 

data-migration/sql-server/managed-instance/guide.md

@@ -29,8 +29,8 @@ Migrate your data using your chosen [migration method](overview.md#compare-migra
 
 - Managed instance link
 - Log Replay Service (LRS)
-- Azure SQL migration extension for Azure Data Studio - migration with near-zero downtime.
 - Native `RESTORE DATABASE FROM URL` - uses native backups from SQL Server and requires some downtime.
+- Azure SQL migration extension for Azure Data Studio - migration with near-zero downtime.
 
 SQL Managed Instance targets user scenarios requiring mass database migration from on-premises or Azure VM database implementations. These are the optimal choice when you need to lift and shift the back end of the applications that regularly use instance level and/or cross-database functionalities. If this is your scenario, you can move an entire instance to a corresponding environment in Azure without the need to rearchitect your applications.
 
@@ -41,27 +41,6 @@ To move SQL instances, you need to plan carefully:
 
 SQL Managed Instance is a managed service that allows you to delegate some of the regular DBA activities to the platform as they're built in. Therefore, some instance-level data doesn't need to be migrated, such as maintenance jobs for regular backups or Always On configuration, as [high availability](/azure/azure-sql/database/high-availability-sla-local-zone-redundancy) is built in.
 
-### Azure Data Studio
-
-This section provides high-level steps to migrate from SQL Server to Azure SQL Managed Instance with minimal downtime by using the Azure SQL migration extension in Azure Data Studio. For detailed instructions, see [Tutorial: Migrate SQL Server to Azure SQL Managed Instance online in Azure Data Studio](/azure/dms/tutorial-sql-server-managed-instance-online-ads).
-
-To migrate with Azure Data Studio, follow these steps:
-
-1. [Download and install Azure Data Studio](/azure-data-studio/download-azure-data-studio) and the [Azure SQL migration extension for Azure Data Studio](/azure-data-studio/extensions/azure-sql-migration-extension).
-1. Launch the **Migrate to Azure SQL Migration** wizard in the extension in Azure Data Studio.
-1. Select databases for assessment and view migration readiness or issues (if any). Additionally, collect performance data and get right-sized Azure recommendation.
-1. Select your Azure account and your target Azure SQL Managed Instance from your subscription.
-1. Select the location of your database backups. Your database backups can either be located on an on-premises network share or in Azure Blob Storage container.
-1. Create a new Azure Database Migration Service using the wizard in Azure Data Studio. If you previously created an Azure Database Migration Service using Azure Data Studio, you can reuse the same if desired.
-1. *Optional*: If your backups are on an on-premises network share, download and install [self-hosted integration runtime](https://www.microsoft.com/download/details.aspx?id=39717) on a machine that can connect to the source SQL Server, and the location containing the backup files.
-1. Start the database migration and monitor the progress in Azure Data Studio. You can also monitor the progress under the Azure Database Migration Service resource in Azure portal.
-1. Complete the cutover.
-   1. Stop all incoming transactions to the source database.
-   1. Make application configuration changes to point to the target database in Azure SQL Managed Instance.
-   1. Take any tail log backups for the source database in the backup location specified.
-   1. Ensure all database backups have the status Restored in the monitoring details page.
-   1. Select Complete cutover in the monitoring details page.
-
 ### Managed Instance link
 
 This section provides high-level steps to migrate from SQL Server to Azure SQL Managed Instance with minimal downtime by using the Managed Instance link. For detailed instructions, review [Migrate with the link](/azure/azure-sql/managed-instance/managed-instance-link-migrate).
@@ -142,6 +121,28 @@ To learn more about this migration option, see [Quickstart: Restore a database t
 > [!NOTE]  
 > A database restore operation is asynchronous and can be retried. You might get an error in SQL Server Management Studio if the connection breaks or a time-out expires. Azure SQL Database will keep trying to restore database in the background, and you can track the progress of the restore using the [sys.dm_exec_requests](/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-requests-transact-sql) and [sys.dm_operation_status](/sql/relational-databases/system-dynamic-management-views/sys-dm-operation-status-azure-sql-database) views.
 
+### Azure Data Studio
+
+This section provides high-level steps to migrate from SQL Server to Azure SQL Managed Instance with minimal downtime by using the Azure SQL migration extension in Azure Data Studio. For detailed instructions, see [Tutorial: Migrate SQL Server to Azure SQL Managed Instance online in Azure Data Studio](/azure/dms/tutorial-sql-server-managed-instance-online-ads).
+
+To migrate with Azure Data Studio, follow these steps:
+
+1. [Download and install Azure Data Studio](/azure-data-studio/download-azure-data-studio) and the [Azure SQL migration extension for Azure Data Studio](/azure-data-studio/extensions/azure-sql-migration-extension).
+1. Launch the **Migrate to Azure SQL Migration** wizard in the extension in Azure Data Studio.
+1. Select databases for assessment and view migration readiness or issues (if any). Additionally, collect performance data and get right-sized Azure recommendation.
+1. Select your Azure account and your target Azure SQL Managed Instance from your subscription.
+1. Select the location of your database backups. Your database backups can either be located on an on-premises network share or in Azure Blob Storage container.
+1. Create a new Azure Database Migration Service using the wizard in Azure Data Studio. If you previously created an Azure Database Migration Service using Azure Data Studio, you can reuse the same if desired.
+1. *Optional*: If your backups are on an on-premises network share, download and install [self-hosted integration runtime](https://www.microsoft.com/download/details.aspx?id=39717) on a machine that can connect to the source SQL Server, and the location containing the backup files.
+1. Start the database migration and monitor the progress in Azure Data Studio. You can also monitor the progress under the Azure Database Migration Service resource in Azure portal.
+1. Complete the cutover.
+   1. Stop all incoming transactions to the source database.
+   1. Make application configuration changes to point to the target database in Azure SQL Managed Instance.
+   1. Take any tail log backups for the source database in the backup location specified.
+   1. Ensure all database backups have the status Restored in the monitoring details page.
+   1. Select Complete cutover in the monitoring details page.
+
+
 ## Data sync and cutover
 
 When using migration options that continuously replicate / sync data changes from source to the target, the source data and schema can change and drift from the target. During data sync, ensure that all changes on the source are captured and applied to the target during the migration process.

data-migration/sql-server/managed-instance/overview.md

@@ -1,5 +1,5 @@
 ---
-title: "SQL Server to SQL Managed Instance: Migration Overview"
+title: "SQL Server to Azure SQL Managed Instance: Migration Overview"
 description: Learn about the tools and options available to migrate your SQL Server databases to Azure SQL Managed Instance.
 author: rwestMSFT
 ms.author: randolphwest
@@ -87,11 +87,11 @@ We recommend the following migration tools:
 
 | Technology | Description |
 | --- | --- |
-| [Azure SQL Migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) | Powered by the [Azure Database Migration service](/azure/dms/dms-overview), the Azure SQL Migration extension for Azure Data Studio helps you to assess your database requirements to understand your migration readiness, get the right-sized SKU recommendations for Azure resources, and migrate your SQL Server database to Azure. You can migrate single databases or at scale using [PowerShell and Azure CLI](/azure/dms/migration-dms-powershell-cli). |
 | [Azure Migrate](/azure/migrate/how-to-create-azure-sql-assessment) | This Azure service helps you discover and assess your SQL data estate at scale on VMware. It provides Azure SQL deployment recommendations, target sizing, and monthly estimates. |
 | [Native backup and restore](/azure/azure-sql/managed-instance/restore-sample-database-quickstart) | SQL Managed Instance supports restore of native SQL Server database backups (.bak files). It's the easiest migration option for customers who can provide full database backups to Azure Storage. |
 | [Log Replay Service](/azure/azure-sql/managed-instance/log-replay-service-migrate) | This cloud service is enabled for SQL Managed Instance based on SQL Server log-shipping technology. It's a migration option for customers who can provide full, differential, and log database backups to Azure Storage. Log Replay Service is used to restore backup files from Azure Blob Storage to SQL Managed Instance. |
 | [Managed Instance link](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview) | This feature enables online migration to SQL Managed Instance by using Always On availability technology to replicate changes nearly real time. It's a migration option for customers who require the database on SQL Managed Instance to be accessible in R/O mode while the migration is in progress, who need to keep the migration running for prolonged periods of time (such as weeks or months at a time), who require true online replication to the Business Critical service tier, and for customers who require the most performant minimum downtime migration. |
+| [Azure Database Migration Service](/data-migration/sql-server/managed-instance/database-migration-service?toc=%2Fazure%2Fdms%2Ftoc.json&tabs=offline-with-extension) | Azure Database Migration Service is a fully managed service designed to enable seamless migrations from multiple database sources to Azure data platforms with minimal downtime. |
 
 The following table lists alternative migration tools:
 
@@ -101,6 +101,7 @@ The following table lists alternative migration tools:
 | [Bulk copy](/sql/relational-databases/import-export/import-and-export-bulk-data-by-using-the-bcp-utility-sql-server) | The [bulk copy program (bcp) tool](/sql/tools/bcp-utility) copies data from an instance of SQL Server into a data file. Use the tool to export the data from your source and import the data file into the target SQL managed instance.<br /><br />For high-speed bulk copy operations to move data to Azure SQL Managed Instance, you can use the [Smart Bulk Copy tool](/samples/azure-samples/smartbulkcopy/smart-bulk-copy/) to maximize transfer speed by taking advantage of parallel copy tasks. |
 | [Import Export Wizard/BACPAC](/azure/azure-sql/database/database-import?tabs=azure-powershell) | [BACPAC](/sql/relational-databases/data-tier-applications/data-tier-applications#bacpac) is a Windows file with a .bacpac extension that encapsulates a database's schema and data. You can use BACPAC to both export data from a SQL Server source and import the data back into Azure SQL Managed Instance. |
 | [Azure Data Factory](/azure/data-factory/connector-azure-sql-managed-instance) | The [Copy activity](/azure/data-factory/copy-activity-overview) in Azure Data Factory migrates data from source SQL Server databases to SQL Managed Instance by using built-in connectors and an [integration runtime](/azure/data-factory/concepts-integration-runtime).<br /><br />Data Factory supports a wide range of [connectors](/azure/data-factory/connector-overview) to move data from SQL Server sources to SQL Managed Instance. |
+| [Azure SQL Migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) | Powered by the [Azure Database Migration service](/azure/dms/dms-overview), the Azure SQL Migration extension for Azure Data Studio helps you to assess your database requirements to understand your migration readiness, get the right-sized SKU recommendations for Azure resources, and migrate your SQL Server database to Azure. You can migrate single databases or at scale using [PowerShell and Azure CLI](/azure/dms/migration-dms-powershell-cli).  | 
 
 ## Compare migration options
 
@@ -111,7 +112,6 @@ The following table compares the recommended migration options:
 | Migration option | When to use | Considerations |
 | --- | --- | --- |
 | [Link feature for Azure SQL Managed Instance](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview) | - Minimum downtime required, especially for critical workloads.<br />- Need to migrate to the Business Critical service tier.<br />- Need to migrate multiple databases.<br />- Need read-only access to the database on Azure SQL Managed Instance during the migration.<br />- Need to reverse migrate out of Azure to SQL Server 2022.<br />- Migrate individual line-of-business application databases, or multiple databases to the same or multiple SQL managed instances.<br />- Need flexibility for the cut over time frame.<br /><br />Supported sources:<br />- SQL Server (2016 to 2022) on-premises or Azure VM<br />- Amazon EC2<br />- GCP Compute SQL Server VM | - The migration entails establishing a network connection between SQL Server and SQL Managed Instance, and opening communication ports.<br />- Uses [distributed availability groups](/sql/database-engine/availability-groups/windows/distributed-availability-groups) technology to replicate database near real-time, making an exact replica of the SQL Server database on SQL Managed Instance.<br />- The database can be used for read-only access on SQL Managed Instance while the migration is in progress.<br />- Provides the best performance during migration with the most minimum downtime.<br />- Can cut over at any time, so migration duration is unlimited<br />- Not affected by system updates or failovers |
-| [Azure SQL Migration extension for Azure Data Studio](/azure/dms/migration-using-azure-data-studio) | - Migrate single databases or at scale.<br />- Can run in both online and offline modes.<br /><br />Supported sources:<br />- SQL Server (2005 onward) on-premises, or on Azure Virtual Machines<br />- SQL Server on Amazon EC2<br />- Amazon RDS for SQL Server<br />- SQL Server on Google Compute Engine | - Migrations at scale can be automated via [PowerShell or Azure CLI](/azure/dms/migration-dms-powershell-cli).<br />- Time to complete migration depends on database size and the number of objects in the database.<br />- Azure Data Studio is required when you aren't using PowerShell or Azure CLI. |
 | [Log Replay Service](/azure/azure-sql/managed-instance/log-replay-service-migrate) | - Migrate individual line-of-business application databases.<br />- Need more control over database migration.<br />- Non-sensitive workloads that can afford downtime.<br />- Can only use a public endpoint.<br />- Need to migrate multiple databases.<br /><br />Supported sources:<br />- SQL Server (2008 to 2022) on-premises or Azure VM<br />- Amazon EC2<br />- Amazon RDS for SQL Server<br />- GCP Compute SQL Server VM | - The migration entails making full database backups on SQL Server and copying backup files to Azure Blob Storage. Log Replay Service is used to restore backup files from Azure Blob Storage to SQL Managed Instance.<br />- Databases during the migration process are in restoring mode and can't be used for read or write workloads until the process is complete.<br />- Uses a public endpoint, so special network configuration isn't necessary.<br />- Can be interrupted by system updates or failovers. |
 | [Native backup and restore](/azure/azure-sql/managed-instance/restore-sample-database-quickstart) | - Migrate individual line-of-business application databases.<br />- Quick and easy migration without a separate migration service or tool.<br /><br />Supported sources:<br />- SQL Server (2005 to 2022) on-premises or Azure VM<br />- Amazon EC2<br />- GCP Compute SQL Server VM | - Database backup uses multiple threads to optimize data transfer to Azure Blob Storage, but partner bandwidth and database size can affect transfer rate.<br />- Downtime should accommodate the time required to perform a full backup and restore (which is a size of data operation). |