3.2. The Azure SQL Family: Choosing the Right Host

💡 First Principle: The choice of database hosting involves a fundamental trade-off between control and convenience—this is the Control-Convenience spectrum from Phase 1 in action. Think of it like choosing between owning a home (full control, full responsibility) versus renting an apartment (less control, maintenance handled for you) versus staying in a hotel (zero control, everything managed). Each Azure SQL option sits somewhere on this spectrum. More control means more responsibility—and more work.

What breaks when you choose wrong? Select SQL Database for a legacy app that uses SQL Agent jobs, and those jobs simply won't run—the feature doesn't exist. Choose SQL on VM for a simple cloud-native app, and you'll spend weekends patching operating systems instead of building features. The cost of a wrong choice is measured in engineering hours, not just dollars.

Scenario: A company migrating to Azure has three SQL Server workloads: (1) A legacy app requiring SQL Server 2012 on Windows Server 2016 with specific OS-level configurations. (2) An enterprise ERP using SQL Agent for job scheduling. (3) A new cloud-native microservice needing a simple, scalable database.

Each workload maps to a different Azure SQL option.