vCore 模型概述vCore model overview

虚拟核心 (vCore) 模型提供以下几项优势:The virtual core (vCore) model provides several benefits:

  • 更高的计算、内存、IO 和存储限制。Higher compute, memory, IO, and storage limits.
  • 控制硬件代系,以便更好地符合工作负荷的计算和内存要求。Control over the hardware generation to better match compute and memory requirements of the workload.
  • 为驱动计算的硬件细节提供更高的透明度;有助于规划从本地部署的迁移。Greater transparency in the hardware details that power the compute; facilitates planning for migrations from on-premises deployments.

服务层Service tiers

vCore 模型中的服务层级选项包括“常规用途”、“业务关键”和“超大规模”。Service tier options in the vCore model include General Purpose, Business Critical, and Hyperscale. 服务层级通常定义存储体系结构、空间和 IO 限制,以及与可用性和灾难恢复相关的业务连续性选项。The service tier generally defines the storage architecture, space and IO limits, and business continuity options related to availability and disaster recovery.

常规用途General purpose 业务关键Business critical 超大规模Hyperscale
最适用于Best for 大多数业务工作负荷。Most business workloads. 提供预算导向的、均衡且可缩放的计算和存储选项。Offers budget-oriented, balanced, and scalable compute and storage options. 它使用多个独立副本为商业应用程序提供最高级别的故障恢复能力,为每个数据库副本提供最高的 I/O 性能。Offers business applications the highest resilience to failures by using several isolated replicas, and provides the highest I/O performance per database replica. 具有很高的可缩放存储和读取缩放要求的大多数业务工作负荷。Most business workloads with highly scalable storage and read-scale requirements. 允许配置多个独立的数据库副本,提供更高的故障恢复能力。Offers higher resilience to failures by allowing configuration of more than one isolated database replica.
存储Storage 使用远程存储。Uses remote storage.
单一数据库和弹性池预配计算Single databases and elastic pools provisioned compute:
5 GB - 4 TB5 GB - 4 TB
无服务器计算Serverless compute:
5 GB - 3 TB5 GB - 3 TB
托管实例:32 GB - 8 TBManaged instance: 32 GB - 8 TB
使用本地 SSD 存储。Uses local SSD storage.
单一数据库和弹性池预配计算Single databases and elastic pools provisioned compute:
5 GB - 4 TB5 GB - 4 TB
托管实例Managed Instance:
32 GB - 2 TB32 GB - 2 TB
可以根据需要灵活地自动扩展存储。Flexible autogrow of storage as needed. 最多支持 100 TB 存储空间。Supports up to 100 TB of storage. 使用本地 SSD 存储作为本地缓冲池缓存和本地数据存储。Uses local SSD storage for local buffer-pool cache and local data storage. 使用 Azure 远程存储作为最终的长期数据存储。Uses Azure remote storage as final long-term data store.
IOPS 和吞吐量(近似值)IOPS and throughput (approximate) 单一数据库和弹性池:请查看单一数据库弹性池的资源限制。Single databases and elastic pools: See resource limits for single databases and elastic pools.
托管实例:请参阅 Azure SQL 数据库托管实例资源限制概述Managed Instance: See Overview Azure SQL Database managed instance resource limits.
请查看单一数据库弹性池的资源限制。See resource limits for single databases and elastic pools. 超大规模是具有多个级别缓存的多层体系结构。Hyperscale is a multi-tiered architecture with caching at multiple levels. 有效的 IOPS 和吞吐量将取决于工作负载。Effective IOPS and throughput will depend on the workload.
可用性Availability 1 个副本,无读取缩放副本1 replica, no read-scale replicas 3 个副本,1 个读取缩放副本3 replicas, 1 read-scale replica 1 个读写副本加 0-4 个读取缩放副本1 read-write replica, plus 0-4 read-scale replicas
备份Backups 读取访问异地冗余存储 (RA-GRS),7-35 天(默认为 7 天)Read-access geo-redundant storage (RA-GRS), 7-35 days (7 days by default) RA-GRS,7-35 天(默认为 7 天)RA-GRS, 7-35 days (7 days by default) Azure 远程存储中基于快照的备份。Snapshot-based backups in Azure remote storage. 还原使用这些快照进行快速恢复。Restores use these snapshots for fast recovery. 备份瞬间完成,不会影响计算 I/O 性能。Backups are instantaneous and don't impact compute I/O performance. 还原速度很快,不基于数据操作的大小(需要几分钟,而不是几小时或几天)。Restores are fast and aren't a size-of-data operation (taking minutes rather than hours or days).
内存中In-memory 不支持Not supported 支持Supported 不支持Not supported

选择服务层级Choosing a service tier

有关为特定工作负荷选择服务层级的信息,请参阅以下文章:For information on selecting a service tier for your particular workload, see the following articles:

计算层级Compute tiers

vCore 模型中的计算层级选项包括预配计算层级和无服务器计算层级。Compute tier options in the vCore model include the provisioned and serverless compute tiers.

预配计算Provisioned compute

预配计算层级提供特定数量的计算资源,这些资源是独立于工作负荷活动持续预配的,针对预配的计算资源量按固定的小时价格计费。The provisioned compute tier provides a specific amount of compute resources that are continuously provisioned independent of workload activity, and bills for the amount of compute provisioned at a fixed price per hour.

无服务器计算Serverless compute

无服务器计算层级根据工作负荷活动自动缩放计算资源,针对使用的计算资源量按秒计费。The serverless compute tier auto-scales compute resources based on workload activity, and bills for the amount of compute used per second.

硬件代系Hardware generations

vCore 模型中的硬件代系选项包括“第 4 代”和“第 5 代”。Hardware generation options in the vCore model include Gen 4/5. 硬件代系通常定义计算和内存限制,以及影响工作负荷性能的其他特征。The hardware generation generally defines the compute and memory limits and other characteristics that impact the performance of the workload.

第 4 代/第 5 代Gen4/Gen5

  • 第 4 代/第 5 代硬件提供均衡的计算和内存资源,适合用于内存和 vCore 要求不太高,或者不需要较快的单一 vCore 的大部分数据库工作负荷,而 Fsv2 系列或 M 系列可以满足这些要求。Gen4/Gen5 hardware provides balanced compute and memory resources, and is suitable for most database workloads that do not have higher memory, higher vCore, or faster single vCore requirements as provided by Fsv2-series or M-series.

有关第 4 代/第 5 代的可用区域,请参阅第 4 代/第 5 代可用性For regions where Gen4/Gen5 is available, see Gen4/Gen5 availability.

计算和内存规格Compute and memory specifications

硬件代次Hardware generation 计算Compute 内存Memory
Gen4Gen4 - Intel E5-2673 v3 (Haswell) 2.4 GHz 处理器- Intel E5-2673 v3 (Haswell) 2.4 GHz processors
- 最多预配 24 个 vCore(1 个 vCore = 1 个物理核心)- Provision up to 24 vCores (1 vCore = 1 physical core)
- 每个 vCore 7 GB- 7 GB per vCore
- 最多预配 168 GB- Provision up to 168 GB
Gen5Gen5 预配计算Provisioned compute
- Intel E5-2673 v4 (Broadwell) 2.3-GHz 和 Intel SP-8160 (Skylake)* 处理器- Intel E5-2673 v4 (Broadwell) 2.3-GHz and Intel SP-8160 (Skylake)* processors
- 最多预配 80 个 vCore(1 个 vCore = 1 个超线程)- Provision up to 80 vCores (1 vCore = 1 hyper-thread)

无服务器计算Serverless compute
- Intel E5-2673 v4 (Broadwell) 2.3-GHz 和 Intel SP-8160 (Skylake)* 处理器- Intel E5-2673 v4 (Broadwell) 2.3-GHz and Intel SP-8160 (Skylake)* processors
- 自动扩展为 16 个 vCore(1 个 vCore = 1 个超线程)- Auto-scale up to 16 vCores (1 vCore = 1 hyper-thread)
预配计算Provisioned compute
- 每个 vCore 5.1 GB- 5.1 GB per vCore
- 最多预配 408 GB- Provision up to 408 GB

无服务器计算Serverless compute
- 自动扩展为每个vCore 24 GB- Auto-scale up to 24 GB per vCore
- 自动扩展为最大 48 GB- Auto-scale up to 48 GB max

* 在 sys.dm_user_db_resource_governance 动态管理视图中,使用 Intel SP-8160 (Skylake) 处理器的 Gen5 数据库的硬件代系会显示为 Gen6。* In the sys.dm_user_db_resource_governance dynamic management view, hardware generation for Gen5 databases using Intel SP-8160 (Skylake) processors appears as Gen6. 不管处理器类型如何(Broadwell 或 Skylake),所有 Gen5 数据库的资源限制都相同。Resource limits for all Gen5 databases are the same regardless of processor type (Broadwell or Skylake).

有关资源限制的详细信息,请参阅单一数据库的资源限制 (vCore)弹性池的资源限制 (vCore)For more information on resource limits, see Resource limits for single databases (vCore), or Resource limits for elastic pools (vCore).

选择硬件代系Selecting a hardware generation

在 Azure 门户中,可以在创建 SQL 数据库或池时为其选择硬件代系,或者更改现有 SQL 数据库或池的硬件代系。In the Azure portal, you can select the hardware generation for a SQL database or pool at the time of creation, or you can change the hardware generation of an existing SQL database or pool.

创建 SQL 数据库或池时选择硬件代系To select a hardware generation when creating a SQL database or pool

有关详细信息,请参阅创建 SQL 数据库For detailed information, see Create a SQL database.

在“基本信息”选项卡上,选择“计算 + 存储”部分中的“配置数据库”链接,然后选择“更改配置”链接: On the Basics tab, select the Configure database link in the Compute + storage section, and then select the Change configuration link:

配置数据库

选择所需的硬件代系:Select the desired hardware generation:

选择硬件

更改现有 SQL 数据库或池的硬件代系To change the hardware generation of an existing SQL database or pool

对于数据库,请在“概述”页上选择“定价层”链接: For a database, on the Overview page, select the Pricing tier link:

更改硬件

对于池,请在“概述”页上选择“配置”。 For a pool, on the Overview page, select Configure.

遵循相应的步骤更改配置,然后根据前面的步骤所述选择硬件代系。Follow the steps to change configuration, and select the hardware generation as described in the previous steps.

创建托管实例时选择硬件代系To select a hardware generation when creating a managed instance

有关详细信息,请参阅创建托管实例For detailed information, see Create a managed instance.

在“基本信息”选项卡上,选择“计算 + 存储”部分中的“配置数据库”链接,然后选择所需的硬件代系: On the Basics tab, select the Configure database link in the Compute + storage section, and then select desired hardware generation:

配置托管实例

更改现有托管实例的硬件代系To change the hardware generation of an existing managed instance

在“托管实例”页上,选择“设置”部分下的“定价层” 链接From the managed instance page, select Pricing tier link placed under the Settings section

更改托管实例硬件

在“定价层” 页上,可以按前面步骤中所述更改硬件代系。On the Pricing tier page you will be able to change hardware generation as described in the previous steps.

硬件可用性Hardware availability

第 4 代/第 5 代Gen4/Gen5

第 5 代可在中国东部 2 和中国北部 2 区域中使用。Gen5 is available in China East 2 and China North 2. 第 4 代可在中国东部和中国北部区域中使用。Gen4 is available in China East and China North.

后续步骤Next steps