Microsoft explains how Hyperscale separates compute, logging and storage while retaining a single primary for writes and SQL Server transaction semantics.
A research-paper retrospective explains how separating query processing, logs, pages and storage changed the scaling behavior of Azure SQL Database.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results