--- title: E1: A reintroduction to Azure SQL Database Hyperscale description: A promotional walkthrough of Azure SQL Database Hyperscale, presented by Microsoft speakers Anna and Bob. They explain that Hyperscale runs on the same SQL... canonical: https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: E1: A reintroduction to Azure SQL Database Hyperscale | daily.dev og:description: A promotional walkthrough of Azure SQL Database Hyperscale, presented by Microsoft speakers Anna and Bob. They explain that Hyperscale runs on the same SQL... og:url: https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead og:image: https://api.daily.dev/og/posts/hfVFcDEAd.png og:image:alt: E1: A reintroduction to Azure SQL Database Hyperscale og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # E1: A reintroduction to Azure SQL Database Hyperscale **[Microsoft Developer](https://daily.dev/sources/microsoftdeveloper)** · 6 min read · 0 upvotes · 0 comments ## Summary A promotional walkthrough of Azure SQL Database Hyperscale, presented by Microsoft speakers Anna and Bob. They explain that Hyperscale runs on the same SQL Server engine but with a different underlying architecture that scales compute and storage independently, supports up to 192 vCores, offers a 99.95% SLA, built-in high availability with named replicas, and security features like versionless customer-managed keys, auditing, and dynamic data masking. A fictionalized lending company, Zopa Lending, is used as an example to demonstrate deploying a Hyperscale database in the Azure portal, provisioning 32 cores with room to scale, and combining customer-facing and internal operations workloads on a single platform. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the maximum number of vCores supported by Azure SQL Database Hyperscale? Azure SQL Database Hyperscale supports up to 192 vCores, along with log rates designed for high-throughput workloads. Storage and compute scale independently, so resources can be adjusted without being locked into a single sizing model, and the service includes built-in high availability with a four-and-a-half nines SLA. _daily.dev helps engineers weighing Hyperscale against other database tiers track scaling limits and SLAs._ ### How does Azure SQL Database Hyperscale handle encryption key rotation? Hyperscale supports data encryption with customer-managed keys as well as versionless keys, meaning the platform automatically picks up new key versions as key rotation occurs, without requiring manual reconfiguration. This is offered alongside other built-in security features such as auditing, ledger for immutable operations, data discovery and classification, and dynamic data masking. _Teams hardening database security follow key rotation and encryption changes like this via daily.dev._ ## Similar posts on daily.dev - [New Azure SQL Foundations video series with GitHub samples](https://daily.dev/posts/new-azure-sql-foundations-video-series-with-github-samples-nkqgttcsx) · DevBlogs · 0 upvotes · 0 comments --- Tags: [#cloud](https://daily.dev/tags/cloud), [#azure](https://daily.dev/tags/azure), [#backend](https://daily.dev/tags/backend) [View this post on daily.dev](https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"E1: A reintroduction to Azure SQL Database Hyperscale","url":"https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead"},"datePublished":"2026-08-24T22:29:02.888Z","dateModified":"2026-09-13T18:33:28.826Z","description":"A promotional walkthrough of Azure SQL Database Hyperscale, presented by Microsoft speakers Anna and Bob. They explain that Hyperscale runs on the same SQL...","image":"https://i.ytimg.com/vi/Gbb4vTh0Lts/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/Gbb4vTh0Lts/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Microsoft Developer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Microsoft Developer","logo":"https://media.daily.dev/image/upload/s--xZzU3zUq--/f_auto/v1746714872/logos/microsoftdeveloper","url":"https://daily.dev/sources/microsoftdeveloper"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cloud,azure,backend","timeRequired":"PT6M","video":{"@type":"VideoObject","name":"E1: A reintroduction to Azure SQL Database Hyperscale","description":"A promotional walkthrough of Azure SQL Database Hyperscale, presented by Microsoft speakers Anna and Bob. They explain that Hyperscale runs on the same SQL...","thumbnailUrl":"https://i.ytimg.com/vi/Gbb4vTh0Lts/sddefault.jpg","uploadDate":"2026-08-24T22:29:02.888Z","duration":"PT6M","url":"https://api.daily.dev/r/hfVFcDEAd","embedUrl":"https://www.youtube.com/embed/Gbb4vTh0Lts"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Microsoft Developer","item":"https://daily.dev/sources/microsoftdeveloper"},{"@type":"ListItem","position":3,"name":"E1: A reintroduction to Azure SQL Database Hyperscale"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/e1-a-reintroduction-to-azure-sql-database-hyperscale-hfvfcdead#faq","mainEntity":[{"@type":"Question","name":"What is the maximum number of vCores supported by Azure SQL Database Hyperscale?","acceptedAnswer":{"@type":"Answer","text":"Azure SQL Database Hyperscale supports up to 192 vCores, along with log rates designed for high-throughput workloads. Storage and compute scale independently, so resources can be adjusted without being locked into a single sizing model, and the service includes built-in high availability with a four-and-a-half nines SLA. daily.dev helps engineers weighing Hyperscale against other database tiers track scaling limits and SLAs."}},{"@type":"Question","name":"How does Azure SQL Database Hyperscale handle encryption key rotation?","acceptedAnswer":{"@type":"Answer","text":"Hyperscale supports data encryption with customer-managed keys as well as versionless keys, meaning the platform automatically picks up new key versions as key rotation occurs, without requiring manual reconfiguration. This is offered alongside other built-in security features such as auditing, ledger for immutable operations, data discovery and classification, and dynamic data masking. Teams hardening database security follow key rotation and encryption changes like this via daily.dev."}}]} ```