--- title: E3: Build AI apps with Azure SQL Database Hyperscale description: Microsoft presenters walk through Azure SQL Database Hyperscale's architecture, which separates compute, storage, page servers, and a log service so each layer... canonical: https://daily.dev/posts/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: E3: Build AI apps with Azure SQL Database Hyperscale | daily.dev og:description: Microsoft presenters walk through Azure SQL Database Hyperscale's architecture, which separates compute, storage, page servers, and a log service so each layer... og:url: https://daily.dev/posts/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z og:image: https://api.daily.dev/og/posts/yx8dNSj1Z.png og:image:alt: E3: Build AI apps with 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. # E3: Build AI apps with Azure SQL Database Hyperscale **[Microsoft Developer](https://daily.dev/sources/microsoftdeveloper)** · 6 min read · 0 upvotes · 0 comments ## Summary Microsoft presenters walk through Azure SQL Database Hyperscale's architecture, which separates compute, storage, page servers, and a log service so each layer can scale independently. Features highlighted include up to 128 TB storage, 192 vCores, 30 named replicas for read scale-out, serverless auto-scaling, elastic pools, and fast snapshot-based point-in-time restores. A demo simulates a fictional lending company scaling from 250 to 2,000 users and 6 million transactions, using columnstore indexes and V-core scaling to maintain predictable cost per transaction and consistent responsiveness while also supporting nightly ETL batch loads. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does Azure SQL Database Hyperscale separate compute and storage? Hyperscale separates compute and storage into distinct scalable layers: a primary replica handling read-write workloads with a buffer pool and SSD cache, page servers providing an additional caching layer over partitioned database data, database files stored on Azure storage, and a separate log service with its own caching that scales independently. HA replicas and page servers pull changes from the log service to stay current. _Architects weighing scalable database designs can track deep dives like this Hyperscale breakdown on daily.dev._ ### What are named replicas in Azure SQL Database Hyperscale and how many can you have? Named replicas are read-scale-out replicas in Azure SQL Database Hyperscale, with up to 30 supported per database. They let read workloads run on a separate compute configuration from the primary replica, which helps reduce costs by right-sizing compute for read-heavy traffic instead of over-provisioning the primary. _Teams planning cost-efficient read scaling can compare approaches like named replicas via daily.dev._ ### What are the maximum storage and compute limits for Azure SQL Database Hyperscale? Azure SQL Database Hyperscale supports up to 128 terabytes of storage, 192 V-cores, 30 named replicas for read scale-out, and four and a half nines of availability, running on AMD EPIC compute optimized for enterprise and AI workloads. These limits are expected to expand further over time. _Developers sizing databases for growth can keep tabs on Hyperscale capacity changes through daily.dev._ --- Tags: [#azure](https://daily.dev/tags/azure), [#backend](https://daily.dev/tags/backend) [View this post on daily.dev](https://daily.dev/posts/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z) ```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":"E3: Build AI apps with Azure SQL Database Hyperscale","url":"https://daily.dev/posts/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z"},"datePublished":"2026-08-24T22:29:03.189Z","dateModified":"2026-09-13T19:46:01.190Z","description":"Microsoft presenters walk through Azure SQL Database Hyperscale's architecture, which separates compute, storage, page servers, and a log service so each layer...","image":"https://i.ytimg.com/vi/RV3GaHKIOvo/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/RV3GaHKIOvo/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/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"azure,backend","timeRequired":"PT6M","video":{"@type":"VideoObject","name":"E3: Build AI apps with Azure SQL Database Hyperscale","description":"Microsoft presenters walk through Azure SQL Database Hyperscale's architecture, which separates compute, storage, page servers, and a log service so each layer...","thumbnailUrl":"https://i.ytimg.com/vi/RV3GaHKIOvo/sddefault.jpg","uploadDate":"2026-08-24T22:29:03.189Z","duration":"PT6M","url":"https://api.daily.dev/r/yx8dNSj1Z","embedUrl":"https://www.youtube.com/embed/RV3GaHKIOvo"}} {"@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":"E3: Build AI apps with Azure SQL Database Hyperscale"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/e3-build-ai-apps-with-azure-sql-database-hyperscale-yx8dnsj1z#faq","mainEntity":[{"@type":"Question","name":"How does Azure SQL Database Hyperscale separate compute and storage?","acceptedAnswer":{"@type":"Answer","text":"Hyperscale separates compute and storage into distinct scalable layers: a primary replica handling read-write workloads with a buffer pool and SSD cache, page servers providing an additional caching layer over partitioned database data, database files stored on Azure storage, and a separate log service with its own caching that scales independently. HA replicas and page servers pull changes from the log service to stay current. Architects weighing scalable database designs can track deep dives like this Hyperscale breakdown on daily.dev."}},{"@type":"Question","name":"What are named replicas in Azure SQL Database Hyperscale and how many can you have?","acceptedAnswer":{"@type":"Answer","text":"Named replicas are read-scale-out replicas in Azure SQL Database Hyperscale, with up to 30 supported per database. They let read workloads run on a separate compute configuration from the primary replica, which helps reduce costs by right-sizing compute for read-heavy traffic instead of over-provisioning the primary. Teams planning cost-efficient read scaling can compare approaches like named replicas via daily.dev."}},{"@type":"Question","name":"What are the maximum storage and compute limits for Azure SQL Database Hyperscale?","acceptedAnswer":{"@type":"Answer","text":"Azure SQL Database Hyperscale supports up to 128 terabytes of storage, 192 V-cores, 30 named replicas for read scale-out, and four and a half nines of availability, running on AMD EPIC compute optimized for enterprise and AI workloads. These limits are expected to expand further over time. Developers sizing databases for growth can keep tabs on Hyperscale capacity changes through daily.dev."}}]} ```