您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

概述 Azure SQL 数据库托管实例的资源限制Overview Azure SQL Database managed instance resource limits

本文提供的资源限制概述 Azure SQL 数据库托管实例,并提供有关如何请求增加这些限制的信息。This article provides an overview of the resource limits for Azure SQL Database managed instance, and provides information about how to request an increase to these limits.

备注

有关支持的功能和 T-SQL 语句的差异,请参阅功能差异T-SQL 语句支持For differences in supported features and T-SQL statements see Feature differences and T-SQL statement support.

实例级别的资源限制Instance-level resource limits

托管的实例具有特征和依赖于底层基础结构和体系结构的资源限制。Managed instance has characteristics and resource limits that depend on the underlying infrastructure and architecture. 这些限制取决于硬件代系和服务层级。Limits depend on hardware generation and service tier.

硬件代系特性Hardware generation characteristics

Azure SQL 数据库托管的实例可以部署在两个硬件代次:Gen4 和 Gen5。Azure SQL Database managed instance can be deployed on two hardware generations: Gen4 and Gen5. 代次的硬件具有不同的特征下, 表中所述:Hardware generations have different characteristics, as described in the following table:

Gen4Gen4 Gen5Gen5
硬件Hardware Intel E5-2673 v3 (Haswell) 2.4-GHz 处理器、附加的 SSD vCore = 1 PP(物理核心)Intel E5-2673 v3 (Haswell) 2.4-GHz processors, attached SSD vCore = 1 PP (physical core) Intel E5-2673 v4 (Broadwell) 2.3-GHz 处理器、快速 NVMe SSD、vCore=1 LP(超线程)Intel E5-2673 v4 (Broadwell) 2.3-GHz processors, fast NVMe SSD, vCore=1 LP (hyper-thread)
vCore 数vCores 8、16、24 个 vCore8, 16, 24 vCores 4、 8、 16、 24、 32、 40、 64,80 个 Vcore4, 8, 16, 24, 32, 40, 64, 80 vCores
内存 (内存/内核之比)Memory (memory/core ratio) 每个 vCore 7 GB7 GB per vCore 每个 vCore 5.1 GB5.1 GB per vCore
最大内存中 OLTP 内存Max In-Memory OLTP memory 实例的限制:每个 vCore 3 GBInstance limit: 3 GB per vCore
数据库限制:Database limits:
-8 核:每个数据库的 8 GB- 8-core: 8 GB per database
-16 核心:每个数据库为 20 GB- 16-core: 20 GB per database
-24 核心:每个数据库的 36 GB- 24-core: 36 GB per database
实例的限制:每个 vCore 2.5 GBInstance limit: 2.5 GB per vCore
数据库限制:Database limits:
-8 核:每个数据库的 13 GB- 8-core: 13 GB per database
-16 核心:每个数据库的 32 GB- 16-core: 32 GB per database
最大实例存储(常规用途)Max instance storage (General Purpose) 8 TB8 TB 8 TB8 TB
最大实例存储(业务关键)Max instance storage (Business Critical) 1 TB1 TB 1 TB、2 TB 或 4 TB,具体取决于核心数1 TB, 2 TB, or 4 TB depending on the number of cores

服务层特征Service tier characteristics

托管的实例都具有两个服务层:“常规用途”和“业务关键”。Managed instance has two service tiers: General Purpose and Business Critical. 这些层提供不同的功能,如下表所述:These tiers provide different capabilities, as described in the table below:

功能Feature 常规用途General Purpose 业务关键Business Critical
vCore 数目*Number of vCores* 第 4 代:8、16、24Gen4: 8, 16, 24
Gen5:4, 8, 16, 24, 32, 40, 64, 80Gen5: 4, 8, 16, 24, 32, 40, 64, 80
Gen4:8、16、24、32Gen4: 8, 16, 24, 32
Gen5:4, 8, 16, 24, 32, 40, 64, 80Gen5: 4, 8, 16, 24, 32, 40, 64, 80
内存Memory Gen4:56 GB - 168 GB (7GB/vCore)Gen4: 56 GB - 168 GB (7GB/vCore)
Gen5:40.8 GB - 408 GB (5.1GB/vCore)Gen5: 40.8 GB - 408 GB (5.1GB/vCore)
Gen4:56 GB - 168 GB (7GB/vCore)Gen4: 56 GB - 168 GB (7GB/vCore)
Gen5:40.8 GB - 408 GB (5.1GB/vCore)Gen5: 40.8 GB - 408 GB (5.1GB/vCore)
最大实例存储大小Max instance storage size -对于 4 个 vcore 数 (仅 Gen5) 2 TB- 2 TB for 4 vCores (Gen5 only)
的有关其他大小 8 TB- 8 TB for other sizes
Gen4:1 TBGen4: 1 TB
Gen5:Gen5:
-1 TB 的 4、 8、 16 个 Vcore- 1 TB for 4, 8, 16 vCores
- 24 个 vCore 2 TB- 2 TB for 24 vCores
- 4 TB(适用于 32、40、64、80 个 vCore)- 4 TB for 32, 40, 64, 80 vCores
每个数据库的最大存储Max storage per database 由每个实例的最大存储大小决定Determined by the max storage size per instance 由每个实例的最大存储大小决定Determined by the max storage size per instance
每个实例的数据库数目上限Max number of databases per instance 100100 100100
每个实例的数据库文件数目上限Max database files per instance 最多 280 个Up to 280 每个数据库 32,767 个文件32,767 files per database
数据/日志 IOPS(近似)Data/Log IOPS (approximate) 500 - 7,500(每个文件)500 - 7,500 per file
*取决于文件大小*Depends on the file size
11 K - 110 K (1375/vCore)11 K - 110 K (1375/vCore)
日志吞吐量Log throughput 3 MB/s(每个 vCore)3 MB/s per vCore
每个实例的最大 22 MB/秒Max 22 MB/s per instance
每个 vCore 4 MB/秒4 MB/s per vCore
最大为 48 MB/秒(每个实例)Max 48 MB/s per instance
数据吞吐量(近似)Data throughput (approximate) 100 - 250 MB/s(每个文件)100 - 250 MB/s per file
*取决于文件大小*Depends on the file size
不适用N/A
IO 延迟(近似)IO latency (approximate) 5-10 毫秒5-10 ms 1-2 毫秒1-2 ms
最大 tempDB 大小Max tempDB size 192 - 1,920 GB(每个 vCore 为 24 GB)192 - 1,920 GB (24 GB per vCore) 无约束 - 受最大实例存储大小限制No constraints - limited by the max instance storage size
最大会话数Max sessions 3000030000 3000030000

备注

  • 与最大存储大小限制进行比较的实例存储大小同时包括用户和系统数据库中的数据及日志文件大小。Both data and log file size in the user and system databases are included in the instance storage size that is compared with the Max storage size limit. 可以使用 sys.master_files 系统视图来确定数据库使用的空间总量。Use sys.master_files system view to determine the total used space by databases. 错误日志不会持久保存,不包括在大小中。Error logs are not persisted and not included in the size. 备份不包括在存储大小中。Backups are not included in storage size.
  • 吞吐量和 IOPS 也取决于显式不受托管实例的页大小。Throughput and IOPS also depend on the page size that is not explicitly limited by managed instance.

支持的区域Supported regions

可以仅在创建托管的实例支持的区域Managed instances can be created only in supported regions. 若要创建的托管的实例目前不支持的区域中,你可以发送一个通过 Azure 门户的支持请求To create a managed instance in a region that is currently not supported, you can send a support request via the Azure portal.

支持的订阅类型Supported subscription types

托管的实例目前支持仅在以下类型的订阅上的部署:Managed instance currently supports deployment only on the following types of subscriptions:

区域资源限制Regional resource limitations

支持的订阅类型针对每个区域可包含有限的资源数。Supported subscription types can contain a limited number of resources per region. 托管的实例,每个 Azure 区域,具体取决于订阅类型的类型有两个默认限制:Managed instance has two default limits per Azure region depending on a type of subscription type:

  • 子网限制:在单一区域中部署托管实例的子网数上限。Subnet limit: The maximum number of subnets where managed instances are deployed in a single region.
  • vCore 限制:最大 vcore 数,可部署在单个区域中的所有实例数。vCore limit: The maximum number of vCores that can be deployed across all instances in a single region.

备注

这些限制是默认设置,不是技术限制。These limits are default settings and not technical limitations. 限制可以增加按需通过创建一个特殊在 Azure 门户中的支持请求如果需要更多托管的实例的当前区域中。The limits can be increased on-demand by creating a special support request in the Azure portal if you need more managed instances in the current region. 或者,可以在另一个 Azure 区域中创建新的托管的实例,而无需发送支持请求。As an alternative, you can create new managed instances in another Azure region without sending support requests.

下表显示了受支持的订阅的默认区域限制:The following table shows the default regional limits for supported subscriptions:

订阅类型Subscription type 托管的实例子网的最大数量Max number of managed instance subnets VCore 单位 * 的最大数量Max number of vCore units*
即用即付Pay-as-you-go 33 320320
CSPCSP 8 (15 中某些区域 * *)8 (15 in some regions**) 960 (1440 中某些区域 * *)960 (1440 in some regions**)
即用即付开发/测试Pay-as-you-go Dev/Test 33 320320
Enterprise 开发/测试Enterprise Dev/Test 33 320320
EAEA 8 (15 中某些区域 * *)8 (15 in some regions**) 960 (1440 中某些区域 * *)960 (1440 in some regions**)
Visual Studio EnterpriseVisual Studio Enterprise 22 6464
Visual Studio Professional 和 MSDN 平台Visual Studio Professional and MSDN Platforms 22 3232

* 当你计划你的部署时,请考虑: vCore 业务关键 (BC) (由于添加了冗余) 所消耗的 4 倍的容量多于常规用途 (GP) vCore。* When you plan your deployments, consider that a Business Critical (BC) vCore (due to added redundancy) consumes 4x more capacity than a General Purpose (GP) vCore. 因此,对于您的计算,1 个 GP vCore = 1 个 vCore 单元和 1 BC vCore = 4 个 vCore 单位。So, for your calculations, 1 GP vCore = 1 vCore unit and 1 BC vCore = 4 vCore units. 若要简化与默认限制您使用的分析,托管的实例部署中,将使用你的订阅类型的实例单位限制结果进行比较的区域中的所有子网间汇总 vCore 单位。To simplify your consumption analysis against the default limits, summarize the vCore units across all subnets in the region where managed instances are deployed and compare the results with the instance unit limits for your subscription type. 最大 vCore 单位数限制适用于区域中的每个订阅。Max number of vCore units limit applies to each subscription in a region. 没有任何限制每个单个子网,但部署跨多个子网的所有 vcore 数之和必须低于或等于最大 vCore 数There is no limit per individual subnets except that the sum of all vCores deployed across multiple subnets must be lower or equal to max number of vCore units.

* * 在以下区域中提供了更大的子网和 vCore 限制:澳大利亚东部、 美国东部、 美国东部 2、 北欧、 美国中南部、 东南亚、 英国南部、 欧洲西部、 美国西部 2。** Larger subnet and vCore limits are available in the following regions: Australia East, East US, East US 2, North Europe, South Central US, Southeast Asia, UK South, West Europe, West US 2.

获取更大配额的 SQL 托管实例Obtaining a larger quota for SQL managed instance

如果需要更多的托管的实例在当前区域中,发送支持请求以扩展使用 Azure 门户的配额。If you need more managed instances in your current regions, send a support request to extend the quota using the Azure portal. 若要启动获取更大配额的过程,请执行以下操作:To initiate the process of obtaining a larger quota:

  1. 打开“帮助 + 支持”,单击“新建支持请求” 。Open Help + support, and click New support request.

    帮助和支持

  2. 在新支持请求的“基本信息”选项卡上:On the Basics tab for the new support request:

    • 对于“问题类型”,选择“服务和订阅限制(配额)” 。For Issue type, select Service and subscription limits (quotas).

    • 对于“订阅”,请选择自己的订阅。 For Subscription, select your subscription.

    • 对于“配额类型”,选择“SQL 数据库托管实例” 。For Quota type, select SQL Database Managed Instance.

    • 对于“支持计划”,选择自己的支持计划 。For Support plan, select your support plan.

      问题类型配额

  3. 单击“下一步”。 Click Next.

  4. 问题选项卡用于新的支持请求:On the Problem tab for the new support request:

    • 对于“严重性”,选择问题的严重性级别 。For Severity, select the severity level of the problem.

    • 对于“详细信息”,提供有关问题的其他信息,包括错误消息 。For Details, provide additional information about your issue, including error messages.

    • 对于“文件上传”,附加包含详细信息的文件(最多 4 MB) 。For File upload, attach a file with more information (up to 4 MB).

      问题详细信息

      重要

      有效的请求应包括:A valid request should include:

      • 限制需要哪种订阅中增加的区域。Region in which subscription limit needs to be increased.
      • 服务层后配额的现有子网中每个 Vcore,所需的数量的增加 (如果现有子网的任何需要先将其展开。Required number of vCores, per service tier in existing subnets after the quota increase (if any of the existing subnets needs to be expanded.
      • 所需的新子网数量和每个新子网中的服务级别的 Vcore 的总行数 (如果您需要部署新的子网中的托管的实例)。Required number of new subnets and total number of vCores per service tier within the new subnets (if you need to deploy managed instances in new subnets).
  5. 单击“下一步”。 Click Next.

  6. 在新支持请求的“联系人信息”选项卡上,输入首选联系方式(电子邮件或电话)和联系人详细信息。On the Contact Information tab for the new support request, enter preferred contact method (email or phone) and the contact details.

  7. 单击创建Click Create.

后续步骤Next steps