5 things you didn't know about Azure SQL Database Hyperscale | Data Exposed
Bob Ward and Anna Hoffman discuss five lesser-known aspects of Azure SQL Database Hyperscale, focusing on what the “Hyperscale” tier really means, how its architecture differs from other tiers, and the practical implications for replicas, backups, and pricing.
Overview
The video highlights key characteristics of the Azure SQL Database Hyperscale service tier and why it behaves differently from other Azure SQL tiers.
1) The “Hyperscale” name: not just for big databases
- Hyperscale isn’t only about supporting very large database sizes; the tier has architectural differences that can matter even when databases aren’t huge.
2) What’s special about the Hyperscale architecture
- Hyperscale uses an architecture that separates storage from compute.
- This separation is positioned as a core reason Hyperscale behaves differently from other service tiers.
3) Replicas and scaling reads
- The presenters discuss named replicas.
- They also cover high availability replicas.
- They call out the ability to “read scale on the fly” (read scaling behavior in Hyperscale).
4) How backups are different
- Hyperscale backups are described as different from other tiers, using snapshot backups.
5) Pricing angle
- The episode mentions Hyperscale being “priced at open-source” (as stated in the chapter list/description), positioning pricing as one of the notable points to understand about the tier.
Resources
- Azure SQL Foundations series: https://aka.ms/azuresqlfoundationseries
- Repos: https://aka.ms/azuresqlfoundations
- Hyperscale FAQ (Microsoft Learn): https://learn.microsoft.com/azure/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq?view=azuresql
People and channels referenced
- Bob Ward (Twitter): https://twitter.com/bobwardms
- Anna Hoffman (Twitter): https://twitter.com/AnalyticAnna
- AzureSQL (Twitter): https://aka.ms/azuresqltw
- Data Exposed episodes: https://aka.ms/dataexposedyt