There are many SQL Server choices available to us as
database architects. This diagram shows the Microsoft database stack available
choices and the business drivers that affect the choice of cost versus administrative
overhead.
An article SQL Server in Azure: Compare PaaS (SQLDB) andIaaS (Virtual Machine)
explains in more depth about the cloud options of SQL
Server in Azure (IaaS) and Azure SQL Database. Igor Pagliai included this useful
table.
Topic
|
Azure
SQLDB (PaaS) |
SQL
Server VM (IaaS) |
| Features | Less features than box | Full box product features |
| Performances | Max 1750 DTU in Premium Tier | Depends on VM SKU/Storage |
| DB Size | Max 1TB in Premium Tier (P11) | 64TB on G-SERIES |
| Workload | Sizing by average usage | Sizing based on peaks |
| High-Availability | Built-in by platform |
Manual configuration by AlwaysOn AG |
| Fault-Handling | Necessary fault-handling & retry |
Recommended fault-handling & retry |
| Locality | No co-location with application | Co-located by VMs and VNETs |
| Segregation | Internet exposed endpoint |
Internal private endpoint |
| Versioning | No control on upgrades |
Full control over DB upgrade |
| TCO | Very low, almost self-managed | High (as on-premise) |
| Administration | No full-time DBA required | Full staffed DBA required |
| Management | Easy to manage many DBs |
Complex to manage many DBs/VMs |
| Scale-Out | Tools & Frameworks available | No easy scale-out |
| Configuration | No setup customization |
Full access to OS and SQL |
| Authentication | Only SQL standard authentication | SQL standard and integrated |
| Security | No Fixed IP available |
Fixed IP possible at VM level |
| Backup | Backup files not accessible | Full control of backup files |
