SQ Azure SQL Blog
Blog

Is Azure SQL Database Hyperscale really distributed SQL?

Azure SQL Database Hyperscale splits a single-writer SQL engine across separate compute, log, page server and storage tiers, so it is distributed in architecture but not in write capacity. The author explains where that line falls against the usual meaning of distributed SQL, and cites a commissioned benchmark against Aurora PostgreSQL. Useful when you choose a database for a growing workload.

Azure SQL operational statistics for PostgreSQL developers

This installment of Microsoft's PostgreSQL-to-SQL field notes compares how each engine helps you diagnose slow queries. It shows which Azure SQL dynamic management views and functions expose in-flight plans, last actual plans, wait statistics and memory grants without preinstalled extensions. Developers moving data access code or troubleshooting Azure SQL performance will find the setup details useful.

Inside Azure SQL Hyperscale: how the Socrates paper split the database

A walkthrough of the 2019 Socrates paper behind Azure SQL Database Hyperscale. The design splits compute, transaction log, page servers and storage into separate tiers, which is why backups, restores and adding replicas no longer scale with database size. Developers running or evaluating Hyperscale get a clear view of the architecture behind it.