A SaaS provider has hundreds of Azure SQL databases with intermittent usage peaks at different times. It wants to share a bounded compute budget across databases. Which design fits?

1. An Azure SQL elastic pool sized for aggregate demand
2. A permanently oversized dedicated compute allocation for every database
3. One storage account per SQL table
4. Geo-replication solely to pool compute