SQL Server to Azure SQL Migration Center¶

The definitive resource for migrating on-premises SQL Server to Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs -- integrated with the CSA-in-a-Box analytics and governance platform.

Who this is for¶

This migration center serves database administrators, data engineers, cloud architects, application developers, and IT leadership who are planning or executing a migration from on-premises SQL Server to Azure. Whether you are responding to end-of-support deadlines, pursuing cost optimization, modernizing your data platform, or meeting federal compliance requirements, these resources provide the assessment tools, migration patterns, and step-by-step guidance to execute confidently.

Quick-start decision matrix¶

Choosing the right Azure SQL target¶

The most critical decision in a SQL Server migration is selecting the right Azure target. Each option optimizes for different priorities.

flowchart TD
    A[On-Premises SQL Server] --> B{Need 100% feature compatibility?}
    B -->|Yes| C{Need OS-level access or<br/>third-party software?}
    C -->|Yes| D[SQL Server on Azure VM]
    C -->|No| E{Need CLR, Service Broker,<br/>cross-DB queries?}
    E -->|Yes| F[Azure SQL Managed Instance]
    E -->|No| G{Single database or<br/>elastic pool?}
    B -->|No| H{Willing to refactor<br/>application code?}
    H -->|Yes| G
    H -->|No| F
    G -->|Single DB| I[Azure SQL Database]
    G -->|Multiple DBs, shared resources| J[Azure SQL Elastic Pool]

    style D fill:#e8f5e9
    style F fill:#e3f2fd
    style I fill:#fff3e0
    style J fill:#fff3e0

Target comparison at a glance¶

How CSA-in-a-Box fits¶

CSA-in-a-Box is not a database migration tool. It is the analytics, governance, and AI platform that makes migrated SQL data productive in the cloud. Once your databases are running on Azure SQL, CSA-in-a-Box provides:

Data governance with Microsoft Purview¶

• Auto-scan Azure SQL databases to discover and classify sensitive data (PII, PHI, financial)
• Data lineage from source SQL tables through ADF/Fabric pipelines to analytics outputs
• Business glossary mapping SQL objects to business-friendly terminology
• Data catalog enabling self-service discovery across all migrated databases

Analytics with Microsoft Fabric¶

• ADF pipelines mirror Azure SQL data into OneLake in Delta Lake format
• dbt models transform raw SQL data through the medallion architecture (bronze/silver/gold)
• Direct Lake semantic models provide sub-second query performance without data duplication
• Power BI reports and dashboards deliver self-service analytics to business users

AI integration¶

• Azure OpenAI enables natural-language queries over migrated SQL data
• AI enrichment pipelines add intelligent classification, summarization, and anomaly detection
• Copilot in Azure SQL provides AI-assisted query tuning and optimization

Monitoring and operations¶

• Azure Monitor provides centralized observability across all Azure SQL instances
• Microsoft Defender for SQL delivers threat detection and vulnerability assessment
• Automated alerting integrates with CSA-in-a-Box operational dashboards

Strategic resources¶

These documents provide the business case, cost analysis, and strategic framing for decision-makers.

Technical references¶

Migration guides¶

Target-specific and domain-specific deep dives covering every aspect of a SQL Server-to-Azure migration.

By target¶

By domain¶

Tutorials¶

Hands-on, step-by-step walkthroughs for common migration scenarios.

Federal and government¶

Timeline overview¶

A typical SQL Server migration follows this timeline, adjusted for estate size:

!!! info "Estate size adjustments" - Small (1-10 databases): Compress to 8-12 weeks total - Medium (11-50 databases): 12-18 weeks with 2-3 migration waves - Large (50+ databases): 18-30 weeks with 4+ migration waves and dedicated migration factory

SQL Server version compatibility¶

All three Azure SQL targets support migration from SQL Server 2008 and later. Older versions require an intermediate upgrade step.

Migration tooling overview¶

Frequently asked questions¶

What is the maximum database size I can migrate?¶

• Azure SQL Database: Up to 100 TB (Hyperscale tier); 4 TB for General Purpose
• Azure SQL Managed Instance: Up to 16 TB
• SQL Server on Azure VM: Limited only by VM storage configuration

How much downtime should I plan for?¶

• Online migration (DMS/LRS/MI Link): Minutes of downtime during cutover
• Offline migration (BACPAC/backup-restore): Hours to days depending on database size
• Transactional replication: Minutes of downtime during subscriber promotion

Can I migrate from SQL Server Express or Developer Edition?¶

Yes. All SQL Server editions (Express, Standard, Enterprise, Developer, Web) can be migrated to any Azure SQL target. Azure SQL pricing is based on the target configuration, not the source edition.

What about SQL Server on Linux?¶

SQL Server on Linux (2017+) can be migrated to Azure SQL using the same tools and approaches. DMS, BACPAC, and backup/restore all support Linux-hosted SQL Server instances.

Can I keep my on-premises SQL Server running during migration?¶

Yes. Online migration modes (DMS, LRS, MI Link, transactional replication) keep the source database fully operational during migration. The source is only impacted at cutover when you stop writes and switch connection strings.

Related¶

• Azure SQL Guide
• SQL Server Integration Guide
• ADF Setup
• Microsoft Purview Guide
• Power BI Guide
• Medallion Architecture Best Practices
• Data Governance Best Practices

References¶

• Azure SQL migration documentation
• Azure Database Migration Service
• Data Migration Assistant
• Azure SQL Migration extension
• Azure Hybrid Benefit
• SQL Server end-of-support
• Microsoft Fabric documentation
• Microsoft Purview documentation