Forum Discussion
babuvt
Apr 06, 2025Copper Contributor
MS SQL in Azure VM to SQL PaaS Migration
What are the current best practices for migrating a SQL Server hosted in an Azure VM to Azure SQL Database?
I’m looking to approach this in two phases: Assessment followed by Migration.
There are several tools available for this process, including Database Migration Assistant (DMA), Azure Data Studio, Azure Migrate, and Azure Database Migration Service (DMS).
The source VMs are running across various OS versions—Windows Server 2008, 2012, 2016, and newer.
However, I’ve noticed that DMA appears to be deprecated, and Azure Data Studio is scheduled for retirement by February 2026.
2 Replies
Sort By
Below some highlight:
Phase 1: Plan and Assess
- Evaluate Compatibility and Readiness:
- Use the Azure SQL Migration extension in Azure Data Studio (recommended replacement for DMA) to assess your SQL Server databases. This tool provides:
- Compatibility analysis for Azure SQL Database.
- Recommendations for right-sizing Azure resources based on performance data.
- Identify Dependencies:
- Analyze application dependencies, SQL Agent jobs, linked servers, and other instance-level features that may not be supported in Azure SQL Database.
- Use Azure Migrate to discover and assess your SQL Server instances and their dependencies.
- Plan for Schema and Data Migration:
- Identify schema changes or data type incompatibilities that need to be addressed before migration.
- Prioritize databases based on business impact and complexity.
Phase 2: Migration
- Choose the Right Migration Tool:
- Azure Database Migration Service (DMS):
- Supports both offline (minimal downtime) and online (near-zero downtime) migrations.
- Ideal for large-scale migrations and continuous data replication.
- Azure SQL Migration Extension in Azure Data Studio:
- Simplifies schema and data migration for smaller workloads or single databases.
- Perform Schema Migration:
- Use DMS or SQL Server Management Studio (SSMS) to export and apply the schema to the target Azure SQL Database.
- Migrate Data:
- For offline migrations, use BACPAC files or DMS.
- For online migrations, configure continuous replication using DMS to minimize downtime.
- Test and Validate:
- Perform thorough testing to ensure data integrity and application functionality.
- Validate performance and scalability in Azure SQL Database.
- Cutover and Optimize:
- Plan a cutover window to switch production workloads to Azure SQL Database.
- Optimize database performance using Query Store and Intelligent Query Processing.
- babuvtCopper Contributor
Thanks for the detailed plan. Given that I have over 50 SQL Servers running on Azure VMs, each hosting multiple instances and numerous databases, is there a way to run the SQL discovery process in batches using Data Studio, rather than connecting to each database individually?