--- title: Is Azure SQL Database Hyperscale “distributed SQL”? description: Azure SQL Database Hyperscale is a distributed architecture with a single-writer SQL engine on top. It splits the jobs a single SQL Server machine used to do... canonical: https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Is Azure SQL Database Hyperscale “distributed SQL”? | daily.dev og:description: Azure SQL Database Hyperscale is a distributed architecture with a single-writer SQL engine on top. It splits the jobs a single SQL Server machine used to do... og:url: https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6 og:image: https://api.daily.dev/og/posts/C29aX5Ny6.png og:image:alt: Is Azure SQL Database Hyperscale “distributed SQL”? 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. # Is Azure SQL Database Hyperscale “distributed SQL”? **[DevBlogs](https://daily.dev/sources/devblogs)** · 4 min read · 0 upvotes · 0 comments ## Summary Azure SQL Database Hyperscale is a distributed architecture with a single-writer SQL engine on top. It splits the jobs a single SQL Server machine used to do across compute replicas, a log service, page servers, and Azure Storage. Storage auto-scales to 128 TB, the log runs at up to 150 MB/s, and compute reaches 192 vCores on Premium-series hardware. A Microsoft-commissioned benchmark against Amazon Aurora PostgreSQL I/O-Optimized on a 2.3 TB database using HammerDB TPROC-C found Hyperscale delivered up to 52% higher performance and up to 51% better performance per dollar at 16 vCores. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Is Azure SQL Database Hyperscale considered distributed SQL? Not in the multi-writer sense. Hyperscale is a distributed architecture, splitting compute, log service, page servers, and storage into separate tiers, but it keeps a single primary that accepts writes. There's no distributed commit protocol or conflict resolution in the write path, so it retains standard SQL Server transaction semantics and full T-SQL compatibility. _daily.dev helps engineers weighing distributed SQL trade-offs track architecture deep-dives like this one._ ### How does Azure SQL Database Hyperscale performance compare to Amazon Aurora PostgreSQL? In a Microsoft-commissioned benchmark by Principled Technologies using HammerDB TPROC-C on a 2.3 TB database, Hyperscale Premium-series beat Amazon Aurora PostgreSQL I/O-Optimized at 16 vCores by up to 52% higher performance and up to 51% better performance per dollar, outperforming at every concurrency level tested. _Teams comparing managed database options for cost and throughput can follow benchmark results like this on daily.dev._ ### What is the maximum storage and compute size for Azure SQL Database Hyperscale? Storage grows automatically up to 128 TB, with near-instant snapshot backups independent of database size. Compute scales up to 192 vCores on Premium-series hardware, the transaction log runs at up to 150 MB/s, and databases can have up to four high-availability replicas plus up to 30 named replicas for isolating reporting or analytics workloads. _Developers sizing databases for growth can track scaling limits like these on daily.dev._ ## Similar posts on daily.dev - [Microsoft Introduces Postgres-Compatible Azure HorizonDB](https://daily.dev/posts/microsoft-introduces-postgres-compatible-azure-horizondb-0ihc5mmlb) · InfoQ · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#database](https://daily.dev/tags/database), [#backend](https://daily.dev/tags/backend), [#azure](https://daily.dev/tags/azure) [View this post on daily.dev](https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6) ```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":"Is Azure SQL Database Hyperscale “distributed SQL”?","url":"https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6"},"datePublished":"2026-10-30T16:55:08.517Z","dateModified":"2026-10-30T17:42:38.295Z","description":"Azure SQL Database Hyperscale is a distributed architecture with a single-writer SQL engine on top. It splits the jobs a single SQL Server machine used to do...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/75f0113972df32ce6e5c4a185f51533c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/75f0113972df32ce6e5c4a185f51533c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DevBlogs","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":"DevBlogs","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8f68b453325f482ebeb73fb780092713","url":"https://daily.dev/sources/devblogs"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,database,backend,azure","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevBlogs","item":"https://daily.dev/sources/devblogs"},{"@type":"ListItem","position":3,"name":"Is Azure SQL Database Hyperscale “distributed SQL”?"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/is-azure-sql-database-hyperscale-distributed-sql--c29ax5ny6#faq","mainEntity":[{"@type":"Question","name":"Is Azure SQL Database Hyperscale considered distributed SQL?","acceptedAnswer":{"@type":"Answer","text":"Not in the multi-writer sense. Hyperscale is a distributed architecture, splitting compute, log service, page servers, and storage into separate tiers, but it keeps a single primary that accepts writes. There's no distributed commit protocol or conflict resolution in the write path, so it retains standard SQL Server transaction semantics and full T-SQL compatibility. daily.dev helps engineers weighing distributed SQL trade-offs track architecture deep-dives like this one."}},{"@type":"Question","name":"How does Azure SQL Database Hyperscale performance compare to Amazon Aurora PostgreSQL?","acceptedAnswer":{"@type":"Answer","text":"In a Microsoft-commissioned benchmark by Principled Technologies using HammerDB TPROC-C on a 2.3 TB database, Hyperscale Premium-series beat Amazon Aurora PostgreSQL I/O-Optimized at 16 vCores by up to 52% higher performance and up to 51% better performance per dollar, outperforming at every concurrency level tested. Teams comparing managed database options for cost and throughput can follow benchmark results like this on daily.dev."}},{"@type":"Question","name":"What is the maximum storage and compute size for Azure SQL Database Hyperscale?","acceptedAnswer":{"@type":"Answer","text":"Storage grows automatically up to 128 TB, with near-instant snapshot backups independent of database size. Compute scales up to 192 vCores on Premium-series hardware, the transaction log runs at up to 150 MB/s, and databases can have up to four high-availability replicas plus up to 30 named replicas for isolating reporting or analytics workloads. Developers sizing databases for growth can track scaling limits like these on daily.dev."}}]} ```