You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -25,7 +25,7 @@ Azure SQL Database lets you easily purchase a fully managed platform as a servic
25
25
26
26
There are two purchasing models:
27
27
28
-
-[vCore-based purchasing model](service-tiers-vcore.md) is available for both [Azure SQL Database](sql-database-paas-overview.md) and [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md). The [Hyperscale service tier](service-tier-Hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
28
+
-[vCore-based purchasing model](service-tiers-vcore.md) is available for both [Azure SQL Database](sql-database-paas-overview.md) and [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md). The [Hyperscale service tier](service-tier-hyperscale.md) is available for single databases that are using the [vCore-based purchasing model](service-tiers-vcore.md).
29
29
-[DTU-based purchasing model](service-tiers-dtu.md) is available for [Azure SQL Database](single-database-manage.md).
30
30
31
31
The following table and chart compares and contrasts the vCore-based and the DTU-based purchasing models:
@@ -65,7 +65,7 @@ Review the table in this section to briefly compare resource limits between Azur
65
65
66
66
To learn more about Azure SQL Database, review the [Hyperscale service tier resource limits](service-tier-hyperscale.md), and DTU resource limits for [single databases](resource-limits-dtu-single-databases.md) and [pooled databases](resource-limits-dtu-elastic-pools.md).
67
67
68
-
To compare features between SQL Database and SQL Managed Instance, see the [database engine features](features-comparison).
68
+
To compare features between SQL Database and SQL Managed Instance, see the [database engine features](features-comparison.md).
69
69
70
70
The following table shows resource limits for both Azure SQL Database and Azure SQL Managed Instance in the Business Critical service tier.
71
71
@@ -83,7 +83,6 @@ The following table shows resource limits for both Azure SQL Database and Azure
83
83
|**Discount models**|[Reserved instances](reserved-capacity-overview.md)<br/>[Azure Hybrid Benefit](../azure-hybrid-benefit.md) (not available on dev/test subscriptions)<br/>[Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/) and [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0023p/) Dev/Test subscriptions|[Reserved instances](reserved-capacity-overview.md)<br/>[Azure Hybrid Benefit](../azure-hybrid-benefit.md) (not available on dev/test subscriptions)<br/>[Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/) and [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0023p/) Dev/Test subscriptions |
@@ -57,7 +57,7 @@ Review the table in this section to briefly compare resource limits between Azur
57
57
58
58
To learn more about Azure SQL Database, review the [Hyperscale service tier resource limits](service-tier-hyperscale.md), and DTU resource limits for [single databases](resource-limits-dtu-single-databases.md) and [pooled databases](resource-limits-dtu-elastic-pools.md).
59
59
60
-
To compare features between SQL Database and SQL Managed Instance, see the [database engine features](features-comparison).
60
+
To compare features between SQL Database and SQL Managed Instance, see the [database engine features](features-comparison.md).
61
61
62
62
The following table shows resource limits for both Azure SQL Database and Azure SQL Managed Instance in the General Purpose service tier:
Copy file name to clipboardExpand all lines: azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ metadata:
11
11
author: dimitri-furman
12
12
ms.author: dfurman
13
13
ms.reviewer: kendralittle, mathoma
14
-
ms.date: 1/10/2022
14
+
ms.date: 02/02/2022
15
15
16
16
title: Azure SQL Database Hyperscale FAQ
17
17
summary: |
@@ -39,7 +39,7 @@ sections:
39
39
- question: |
40
40
How does the Hyperscale service tier differ from the General Purpose and Business Critical service tiers?
41
41
answer: |
42
-
The vCore-based service tiers are differentiated based on database availability and storage type, performance, and maximum size, as described in the following table. To learn more, compare [resource limits between service tiers](service-tier-hyperscale.md#compare-resource-limits)
42
+
The vCore-based service tiers are differentiated based on database availability and storage type, performance, and maximum storage size as described in [resource limit comparison](service-tier-hyperscale.md#compare-resource-limits).
The vCore-based service tiers are differentiated based on database availability and storage type, performance, and maximum size, as described in the following table:
92
-
93
-
|| Resource type | General Purpose | Hyperscale | Business Critical |
94
-
|:---:|:---:|:---:|:---:|:---:|
95
-
|**Best for**|All|Offers budget oriented balanced compute and storage options.|Most business workloads. Autoscaling storage size up to 100 TB,fast vertical and horizontal compute scaling, fast database restore.|OLTP applications with high transaction rate and low IO latency. Offers highestresilience to failures and fast failovers using multiple synchronously updated replicas.|
|**IOPS**| Single database | 500 IOPS per vCore with 7000 maximum IOPS | Hyperscale is a multi-tiered architecture with caching at multiplelevels. Effective IOPS will depend on the workload. | 5000 IOPS with 200,000 maximum IOPS|
101
-
|**Availability**|All|1 replica, no Read Scale-out, zone-redundant HA (preview), no local cache | Multiple replicas, up to 4 Read Scale-out, partiallocal cache | 3 replicas, 1 Read Scale-out, zone-redundant HA, full local storage |
102
-
|**Backups**|All| A choice of geo-redundant, zone-redundant <sup>2</sup> , or locally-redundant<sup>2</sup> backup storage, 1-35 day retention (default 7 days) | A choice of geo-redundant, zone-redundant <sup>3</sup>, or locally-redundant<sup>3</sup> backup storage, 7 day retention. | A choice of geo-redundant,zone-redundant<sup>2</sup>, or locally-redundant<sup>2</sup> backup storage, 1-35 day retention (default 7 days) |
103
-
||||||
89
+
The vCore-based service tiers are differentiated based on database availability and storage type, performance, and maximum storagesize, as described in the following table:
90
+
91
+
|| General Purpose | Hyperscale | Business Critical |
92
+
|:---:|:---:|:---:|:---:|
93
+
|**Best for**|Offers budget oriented balanced compute and storage options.|Most business workloads. Autoscaling storage size up to 100 TB,fast vertical and horizontal compute scaling, fast database restore.|OLTP applications with high transaction rate and low IO latency. Offers highestresilience to failures and fast failovers using multiple synchronously updated replicas.|
|**Compute size**| 1 to 80 vCores | 1 to 80 vCores<sup>1</sup>| 1 to 80 vCores |
96
+
|**Storage type**| Premium remote storage (per instance) | De-coupled storage with local SSD cache (per instance) | Super-fast local SSDstorage (per instance) |
97
+
|**Storage size**<sup>1</sup> 5 GB – 4 TB | Up to 100 TB | 5 GB – 4 TB |
98
+
|**IOPS**| 500 IOPS per vCore with 7000 maximum IOPS | Hyperscale is a multi-tiered architecture with caching at multiplelevels. Effective IOPS will depend on the workload. | 5000 IOPS with 200,000 maximum IOPS|
99
+
|**Availability**| 1 replica, no Read Scale-out, zone-redundant HA (preview), no local cache | Multiple replicas, up to 4 Read Scale-out, partiallocal cache | 3 replicas, 1 Read Scale-out, zone-redundant HA, full local storage |
100
+
|**Backups**| A choice of geo-redundant, zone-redundant <sup>2</sup> , or locally-redundant<sup>2</sup> backup storage, 1-35 day retention (default 7 days) | A choice of geo-redundant, zone-redundant <sup>3</sup>, or locally-redundant<sup>3</sup> backup storage, 7 day retention. | A choice of geo-redundant,zone-redundant<sup>2</sup>, or locally-redundant<sup>2</sup> backup storage, 1-35 day retention (default 7 days) |
101
+
||||
104
102
105
103
<sup>1</sup> Elastic pools are not supported in the Hyperscale service tier
||DTU-based purchasing model|The [Database Transaction Unit (DTU)-based purchasing model](database/service-tiers-dtu.md) is based on a bundled measure of compute, storage, and I/O resources. Compute sizes are expressed in DTUs for single databases and in elastic database transaction units (eDTUs) for elastic pools. |
31
31
||vCore-based purchasing model (recommended)| A virtual core (vCore) represents a logical CPU. The [vCore-based purchasing model](database/service-tiers-vcore.md) offers greater control over the hardware configuration to better match compute and memory requirements of the workload, pricing discounts for [Azure Hybrid Benefit (AHB)](azure-hybrid-benefit.md) and [Reserved Instance (RI)](database/reserved-capacity-overview.md), more granular scaling, and greater transparency in hardware details. Newer capabilities (for example, hyperscale, serverless) are only available in the vCore model. |
32
32
|Service tier|| The service tier defines the storage architecture, storage and I/O limits, and business continuity options. Options for service tiers vary by purchasing model. |
33
-
||DTU-based service tiers |[Basic, standard, and premium service tiers](database/service-tiers-dtu.md#compare-the-dtu-based-service-tiers) are available in the DTU-based purchasing model.|
33
+
||DTU-based service tiers |[Basic, standard, and premium service tiers](database/service-tiers-dtu.md#compare-service-tiers) are available in the DTU-based purchasing model.|
34
34
||vCore-based service tiers (recommended) |[General purpose, business critical, and hyperscale service tiers](database/service-tiers-sql-database-vcore.md#service-tiers) are available in the vCore-based purchasing model (recommended).|
35
35
|Compute tier|| The compute tier determines whether resources are continuously available (provisioned) or autoscaled (serverless). Compute tier availability varies by purchasing model and service tier. Only the vCore purchasing model's general purpose service tier makes serverless compute available.|
36
36
||Provisioned compute|The [provisioned compute tier](database/service-tiers-sql-database-vcore.md#compute-tiers) provides a specific amount of compute resources that are continuously provisioned independent of workload activity. Under the provisioned compute tier, you are billed at a fixed price per hour.
0 commit comments