Modern models of managing database fleets in Azure PaaS.
summary
Azure Database Fleet Manager automates tenant provisioning, placement, autoscaling and pool rebalancing for Azure SQL with a stable connection endpoint so application connection strings stay immutable even when databases move. Fleet Manager provisions elastic pools, enforces per-tier caps (example: bronze 2 vCore pools with 100 DBs/pool; example tier limits like 4 vCores per DB and 50 DBs/pool shown), runs competing cost vs performance moves, exposes a one‑line provisioning API that returns a connection string, and is available in private preview with portal presets like bronze/silver/gold.
AI-written summary · about
chapters (8)
- 0:00Azure fleet management intro
- 22:24Fleet manager architecture
- 24:13Autonomous placement & load balancing
- 27:04User roles in fleet management
- 29:08Database tiers in Azure portal
- 33:29App integration & tenant provisioning
- 34:54Fleet manager benefits & future
- 37:25Q&A on caching & tuning
related talks
48mBuilding SaaS solutions on Azure SQL Database
46mDatabase-Per-Tenant Architecture Using .Net Core and Azure SQL Database
51mFly at Mach-speed with Azure SQL Managed Instance
20mChoosing the Right Data Store--An Overview of Azure Data Platform Choices
18mHow to reduce your SQL Database costs on Azure
01h 11mHand-On-Labs: How crazy are these from Azure Database PaaS!
52mAzure Sql DB Managed instance, a different sql server?
50mSQL Server to Azure SQL: Performance and Availability