[KongchangAI]
ProductHyperscale / Azure Hyperscale

Azure SQL Database Hyperscale

A next-generation cloud database architecture introduced by Microsoft in 2018 that fully decouples the compute and storage layers. Storage capacity can scale beyond 100 TB, read replicas can be added rapidly, and pricing is comparable to mainstream open-source databases.

Timeline (last 90 days)

Oct 20

The Hyperscale compute layer can scale up to 192 vCores, and scaling compute does not require moving the database.

Unverified50%
Oct 20

Hyperscale supports up to 30 named replicas, each of which can be configured independently with compute resources to isolate read-intensive workloads.

Unverified50%
Oct 20

Hyperscale offers an availability SLA of up to 99.995% when configured with zone redundancy.

Unverified50%
Oct 20

The Hyperscale log service can provide transaction log throughput of up to 150 MB/s, independent of the compute size of the primary replica.

Unverified50%
Oct 20

A named replica is a read-only compute replica in Hyperscale used for read scale-out, with its own connection endpoint, that does not participate in automatic failover and shares the primary replica's page servers and storage layer.

Unverified50%
Oct 20

A page server is a core storage component in the Hyperscale architecture that manages a portion of the database's data pages and maintains its own SSD cache, consumes transaction log records and persists updates to Azure Storage.

Unverified50%
Oct 20

Resilient Buffer Pool Extension is a local SSD caching mechanism on Hyperscale compute replicas used to extend memory buffer pool capacity and reduce remote requests to page servers.

Unverified50%
Oct 20

Hyperscale can be configured with 0 to 4 high-availability replicas as hot standby compute for automatic failover, and adding a high-availability replica does not require creating another full copy of the database.

Unverified50%
Oct 20

Hyperscale backup and restore are performed using file snapshots at the storage layer, and same-region restore can complete within minutes, with restore time no longer growing linearly with database size.

Unverified50%
Oct 20

The Hyperscale Premium series configuration can reach up to 192 vCores, 843 GB of memory and 816,000 local SSD IOPS.

Unverified50%

1 more timeline events

All Facts (13)

Unverified

Hyperscale's Continuous Priming mechanism tracks active pages accessed by the primary replica, which are fed back to high-availability replicas by the page servers to shorten performance recovery time after failover.

50%
Unverified

Hyperscale backup and restore are performed using file snapshots at the storage layer, and same-region restore can complete within minutes, with restore time no longer growing linearly with database size.

50%
Unverified

The Hyperscale Premium series configuration can reach up to 192 vCores, 843 GB of memory and 816,000 local SSD IOPS.

50%
Unverified

The Hyperscale compute layer can scale up to 192 vCores, and scaling compute does not require moving the database.

50%
Unverified

Hyperscale supports up to 30 named replicas, each of which can be configured independently with compute resources to isolate read-intensive workloads.

50%
Unverified

Hyperscale offers an availability SLA of up to 99.995% when configured with zone redundancy.

50%
Unverified

The Hyperscale log service can provide transaction log throughput of up to 150 MB/s, independent of the compute size of the primary replica.

50%
Unverified

A named replica is a read-only compute replica in Hyperscale used for read scale-out, with its own connection endpoint, that does not participate in automatic failover and shares the primary replica's page servers and storage layer.

50%
Unverified

A page server is a core storage component in the Hyperscale architecture that manages a portion of the database's data pages and maintains its own SSD cache, consumes transaction log records and persists updates to Azure Storage.

50%
Unverified

Resilient Buffer Pool Extension is a local SSD caching mechanism on Hyperscale compute replicas used to extend memory buffer pool capacity and reduce remote requests to page servers.

50%
Unverified

Hyperscale can be configured with 0 to 4 high-availability replicas as hot standby compute for automatic failover, and adding a high-availability replica does not require creating another full copy of the database.

50%
Unverified

Hyperscale 数据库存储容量理论上可扩展至100TB以上

50%
Unverified

Azure SQL Database Hyperscale 是微软于2018年推出的新一代云数据库架构

50%

Source Articles