--- title: The Developers Guide to Azure SQL Hyperscale | daily.dev description: A Microsoft principal architect walks through Azure SQL Hyperscale's architecture and capabilities in a conference session, covering its distributed... canonical: https://daily.dev/posts/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The Developers Guide to Azure SQL Hyperscale | daily.dev og:description: A Microsoft principal architect walks through Azure SQL Hyperscale's architecture and capabilities in a conference session, covering its distributed... og:url: https://daily.dev/posts/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae og:image: https://api.daily.dev/og/posts/xvjgaeSaE.png og:image:alt: The Developers Guide to Azure SQL 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. # The Developers Guide to Azure SQL Hyperscale **[Microsoft Developer](https://daily.dev/sources/microsoftdeveloper)** · 74 min read · 1 upvotes · 0 comments ## Summary A Microsoft principal architect walks through Azure SQL Hyperscale's architecture and capabilities in a conference session, covering its distributed compute/storage separation, page servers, log service, named replicas, and fast point-in-time restore (40TB in 7 minutes). The session dispels the myth that Hyperscale is only for huge databases, noting it starts at 2 vCores and 10GB and scales to 192 vCores and 128TB. A live demo shows a hospital app built with GitHub Copilot, using managed identity for passwordless auth, row-level security with session context, vector search on named replicas, and an AI agent via Data API Builder and MCP for clinical assistance, plus new features like change event streaming and versionless customer-managed keys. ## 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 minimum number of vCores required for an Azure SQL Hyperscale database? The minimum is 2 vCores. A Hyperscale database can scale from that minimum up to 192 vCores, and storage independently scales from a 10 GB starting point up to 128 TB, letting teams start small and grow into much larger workloads without re-architecting. _Developers sizing a new database can track scaling limits like this on daily.dev before committing to an architecture._ ### How fast can Azure SQL Hyperscale perform a point-in-time restore on a large database? A 40 TB Hyperscale database can be restored to a point in time in about 7 minutes. This speed comes from the architecture's separation of compute and storage, snapshot-based backups, and a dedicated log service that applies incremental snapshots plus log changes instead of replaying a full backup chain. _Anyone evaluating disaster recovery options can compare restore speeds like this on daily.dev._ ### Does Azure SQL Hyperscale charge a SQL Server license fee? No, Hyperscale does not require a SQL Server license fee; customers pay only for the compute and storage they use, billed separately, and storage size does not dictate compute size. Reserved capacity or a savings plan can reduce costs by up to 55%, and zone-redundant Hyperscale ends up costing roughly the same as a zone-redundant general purpose database. _Teams comparing managed database pricing can weigh options like this on daily.dev before choosing a service tier._ ## 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: [#azure](https://daily.dev/tags/azure), [#backend](https://daily.dev/tags/backend), [#microsoft-sql-server](https://daily.dev/tags/microsoft-sql-server) [View this post on daily.dev](https://daily.dev/posts/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae) ```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":"The Developers Guide to Azure SQL Hyperscale","url":"https://daily.dev/posts/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae"},"datePublished":"2026-08-19T16:03:26.189Z","dateModified":"2026-09-14T09:13:17.391Z","description":"A Microsoft principal architect walks through Azure SQL Hyperscale's architecture and capabilities in a conference session, covering its distributed...","image":"https://i.ytimg.com/vi/PS2U-mZYvss/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/PS2U-mZYvss/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/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"azure,backend,microsoft-sql-server","timeRequired":"PT74M","video":{"@type":"VideoObject","name":"The Developers Guide to Azure SQL Hyperscale","description":"A Microsoft principal architect walks through Azure SQL Hyperscale's architecture and capabilities in a conference session, covering its distributed...","thumbnailUrl":"https://i.ytimg.com/vi/PS2U-mZYvss/sddefault.jpg","uploadDate":"2026-08-19T16:03:26.189Z","duration":"PT74M","url":"https://api.daily.dev/r/xvjgaeSaE","embedUrl":"https://www.youtube.com/embed/PS2U-mZYvss"}} {"@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":"The Developers Guide to Azure SQL Hyperscale"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-developers-guide-to-azure-sql-hyperscale-xvjgaesae#faq","mainEntity":[{"@type":"Question","name":"What is the minimum number of vCores required for an Azure SQL Hyperscale database?","acceptedAnswer":{"@type":"Answer","text":"The minimum is 2 vCores. A Hyperscale database can scale from that minimum up to 192 vCores, and storage independently scales from a 10 GB starting point up to 128 TB, letting teams start small and grow into much larger workloads without re-architecting. Developers sizing a new database can track scaling limits like this on daily.dev before committing to an architecture."}},{"@type":"Question","name":"How fast can Azure SQL Hyperscale perform a point-in-time restore on a large database?","acceptedAnswer":{"@type":"Answer","text":"A 40 TB Hyperscale database can be restored to a point in time in about 7 minutes. This speed comes from the architecture's separation of compute and storage, snapshot-based backups, and a dedicated log service that applies incremental snapshots plus log changes instead of replaying a full backup chain. Anyone evaluating disaster recovery options can compare restore speeds like this on daily.dev."}},{"@type":"Question","name":"Does Azure SQL Hyperscale charge a SQL Server license fee?","acceptedAnswer":{"@type":"Answer","text":"No, Hyperscale does not require a SQL Server license fee; customers pay only for the compute and storage they use, billed separately, and storage size does not dictate compute size. Reserved capacity or a savings plan can reduce costs by up to 55%, and zone-redundant Hyperscale ends up costing roughly the same as a zone-redundant general purpose database. Teams comparing managed database pricing can weigh options like this on daily.dev before choosing a service tier."}}]} ```