Introduction
In the previous article, we introduced Azure SQL and its three primary deployment options:
Azure SQL Database
Azure SQL Managed Instance
SQL Server on Azure Virtual Machines
One of the most important decisions when moving SQL Server workloads to Microsoft Azure is selecting the right platform.
Choosing the wrong platform can result in unnecessary migration effort, higher operational overhead, performance limitations, or unexpected costs.
This article explains the differences from a practical DBA and migration perspective.
1. Azure SQL Database
Azure SQL Database is a fully managed Platform as a Service (PaaS) offering.
Microsoft manages the underlying operating system, hardware, database engine infrastructure, patching, and much of the high-availability architecture.
The DBA primarily focuses on:
Database configuration
Security
Performance
Query tuning
Indexes
Data management
Cost optimization
Monitoring
A typical architecture is:
Application
|
v
Azure SQL Database
|
+---- Backup
+---- Monitoring
+---- Security
+---- High Availability
When should you consider Azure SQL Database?
Azure SQL Database is particularly suitable for:
New cloud-native applications
Modern application architectures
Individual databases
Applications that do not require extensive instance-level SQL Server features
Organizations looking to minimize infrastructure administration
The major benefit is reduced operational overhead.
2. Azure SQL Managed Instance
Azure SQL Managed Instance is also a PaaS service, but it provides a broader set of SQL Server capabilities than Azure SQL Database.
This makes it particularly interesting for organizations migrating existing SQL Server applications.
For example:
Existing SQL Server
|
| Assessment
v
Azure SQL Managed Instance
|
v
Application
Managed Instance can reduce the number of changes required during migration compared with moving directly to Azure SQL Database.
It is therefore commonly considered when the existing SQL Server environment depends on features that are more closely aligned with an instance-based SQL Server architecture.
3. SQL Server on Azure Virtual Machines
SQL Server on Azure Virtual Machines is an Infrastructure as a Service (IaaS) model.
You essentially run SQL Server on an Azure VM.
The architecture looks like:
Application
|
v
Azure VM
|
+---- Windows/Linux
|
+---- SQL Server
|
+---- Data Disks
|
+---- Backup
|
+---- Monitoring
This provides the DBA with significantly more control.
You can manage:
Operating system
SQL Server version
SQL Server configuration
Instance-level settings
Storage layout
SQL Agent
Maintenance jobs
Backup configuration
Custom monitoring
Third-party software
However, that flexibility also means additional administration.
4. PaaS vs IaaS
The fundamental difference can be summarized as:
Area | Azure SQL Database | Azure SQL Managed Instance | SQL Server on Azure VM |
|---|---|---|---|
Service model | PaaS | PaaS | IaaS |
OS management | Microsoft | Microsoft | Customer |
SQL Server installation | Managed | Managed | Customer |
Instance-level control | Limited | Higher | Highest |
Infrastructure management | Low | Low | High |
SQL Server compatibility | Application dependent | High | Highest |
Migration effort | Can be higher | Often lower for existing SQL Server | Usually lowest from infrastructure perspective |
Custom OS configuration | No | No | Yes |
Jasen FiciPosted Oct 29, 2026, 12:46 PM
This was included in DotNetNews here: https://dotnetnews.beehiiv.com/p/new-post-5a02