使用 DTU 购买模型的单一数据库的资源限制 - Azure SQL 数据库Resource limits for single databases using the DTU purchasing model - Azure SQL Database
适用于：
Azure SQL 数据库
本文提供了针对使用 DTU 购买模型的 Azure SQL 数据库的单一数据库的详细资源限制。This article provides the detailed resource limits for Azure SQL Database single databases using the DTU purchasing model.
有关弹性池的 DTU 购买模型资源限制，请参阅 DTU 资源限制 - 弹性池。For DTU purchasing model resource limits for elastic pools, see DTU resource limits - elastic pools. 有关 vCore 资源限制，请参阅 vCore 资源限制 - 单一数据库和 vCore 资源限制 - 弹性池。For vCore resource limits, see vCore resource limits - single databases and vCore resource limits - elastic pools. 有关不同购买模型的更多信息，请参阅购买模型和服务层级。For more information regarding the different purchasing models, see Purchasing models and service tiers.
单一数据库：存储大小和计算大小Single database: Storage sizes and compute sizes
下表显示了可用于每个服务层级和计算大小的单一数据库的资源。The following tables show the resources available for a single database at each service tier and compute size. 可通过 Azure 门户、Transact-SQL、PowerShell、Azure CLI 或 REST API 为单一数据库设置服务层级、计算大小和存储量。You can set the service tier, compute size, and storage amount for a single database using the Azure portal, Transact-SQL, PowerShell, the Azure CLI, or the REST API.
重要
有关缩放指南和注意事项，请参阅缩放单一数据库For scaling guidance and considerations, see Scale a single database
“基本”服务层级Basic service tier
| 计算大小Compute size | 基本Basic |
|---|---|
| 最大 DTU 数Max DTUs | 55 |
| 包含的存储 (GB)Included storage (GB) | 22 |
| 最大存储 (GB)Max storage (GB) | 22 |
| 最大内存中 OLTP 存储 (GB)Max in-memory OLTP storage (GB) | 空值N/A |
| 最大并发工作线程数（请求数）Max concurrent workers (requests) | 3030 |
| 最大并发会话数Max concurrent sessions | 300300 |
重要
“基本”服务层级提供的 vCore (CPU) 不到一个。The Basic service tier provides less than one vCore (CPU). 对于 CPU 密集型工作负荷，建议使用 S3 或更高的服务层级。For CPU-intensive workloads, a service tier of S3 or greater is recommended.
有关数据存储的“基本”服务层级放置在标准页 Blob 上。Regarding data storage, the Basic service tier is placed on Standard Page Blobs. 标准页 Blob 使用基于硬盘驱动器 (HDD) 的存储介质，最适合用于对性能变化不太敏感的开发、测试和其他不频繁访问的工作负荷。Standard Page Blobs use hard disk drive (HDD)-based storage media and are best suited for development, testing, and other infrequently accessed workloads that are less sensitive to performance variability.
“标准”服务层级Standard service tier
| 计算大小Compute size | S0S0 | S1S1 | S2S2 | S3S3 |
|---|---|---|---|---|
| 最大 DTUMax DTUs | 10 个10 | 20 个20 | 5050 | 100100 |
| 包含的存储 (GB) 1Included storage (GB) 1 | 250250 | 250250 | 250250 | 250250 |
| 最大存储 (GB)Max storage (GB) | 250250 | 250250 | 250250 | 10241024 |
| 最大内存中 OLTP 存储 (GB)Max in-memory OLTP storage (GB) | 空值N/A | 空值N/A | 空值N/A | 空值N/A |
| 最大并发工作线程数（请求数）Max concurrent workers (requests) | 6060 | 9090 | 120120 | 200200 |
| 最大并发会话数Max concurrent sessions | 600600 | 900900 | 12001200 | 24002400 |
1 请参阅 SQL 数据库定价选项，详细了解由于任何预配的额外存储导致的额外成本。1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.
重要
标准 S0、S1 和 S2 层级提供的 vCore (CPU) 不到一个。The Standard S0, S1 and S2 tiers provide less than one vCore (CPU). 对于 CPU 密集型工作负荷，建议使用 S3 或更高的服务层级。For CPU-intensive workloads, a service tier of S3 or greater is recommended.
有关数据存储的标准 S0 和 S1 服务层级放置在标准页 Blob 上。Regarding data storage, the Standard S0 and S1 service tiers are placed on Standard Page Blobs. 标准页 Blob 使用基于硬盘驱动器 (HDD) 的存储介质，最适合用于对性能变化不太敏感的开发、测试和其他不频繁访问的工作负荷。Standard Page Blobs use hard disk drive (HDD)-based storage media and are best suited for development, testing, and other infrequently accessed workloads that are less sensitive to performance variability.
“标准”服务层级（续）Standard service tier (continued)
| 计算大小Compute size | S4S4 | S6S6 | S7S7 | S9S9 | S12S12 |
|---|---|---|---|---|---|
| 最大 DTU 数Max DTUs | 200200 | 400400 | 800800 | 16001600 | 30003000 |
| 包含的存储 (GB) 1Included storage (GB) 1 | 250250 | 250250 | 250250 | 250250 | 250250 |
| 最大存储 (GB)Max storage (GB) | 10241024 | 10241024 | 10241024 | 10241024 | 10241024 |
| 最大内存中 OLTP 存储 (GB)Max in-memory OLTP storage (GB) | 空值N/A | 空值N/A | 空值N/A | 空值N/A | 空值N/A |
| 最大并发工作线程数（请求数）Max concurrent workers (requests) | 400400 | 800800 | 16001600 | 32003200 | 60006000 |
| 最大并发会话数Max concurrent sessions | 48004800 | 96009600 | 1920019200 | 3000030000 | 3000030000 |
1 请参阅 SQL 数据库定价选项，详细了解由于任何预配的额外存储导致的额外成本。1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.
“高级”服务层级Premium service tier
| 计算大小Compute size | P1P1 | P2P2 | P4P4 | P6P6 | P11P11 | P15P15 |
|---|---|---|---|---|---|---|
| 最大 DTU 数Max DTUs | 125125 | 250250 | 500500 | 10001000 | 17501750 | 40004000 |
| 包含的存储 (GB) 1Included storage (GB) 1 | 500500 | 500500 | 500500 | 500500 | 4096 24096 2 | 4096 24096 2 |
| 最大存储 (GB)Max storage (GB) | 10241024 | 10241024 | 10241024 | 10241024 | 4096 24096 2 | 4096 24096 2 |
| 最大内存中 OLTP 存储 (GB)Max in-memory OLTP storage (GB) | 11 | 22 | 44 | 88 | 1414 | 3232 |
| 最大并发工作线程数（请求数）Max concurrent workers (requests) | 200200 | 400400 | 800800 | 16001600 | 28002800 | 64006400 |
| 最大并发会话数Max concurrent sessions | 3000030000 | 3000030000 | 3000030000 | 3000030000 | 3000030000 | 3000030000 |
1 请参阅 SQL 数据库定价选项，详细了解由于任何预配的额外存储导致的额外成本。1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.
2 从 1024 GB 到 4096 GB，以 256 GB 为增量。2 From 1024 GB up to 4096 GB in increments of 256 GB.
备注
有关 tempdb 限制，请参阅 tempdb 限制。For tempdb limits, see tempdb limits.
后续步骤Next steps
- 有关单一数据库的 vCore 资源限制，请参阅使用 vCore 购买模型的单一数据库的资源限制For vCore resource limits for a single database, see resource limits for single databases using the vCore purchasing model
- 有关弹性池的 vCore 资源限制，请参阅使用 vCore 购买模型的弹性池的资源限制For vCore resource limits for elastic pools, see resource limits for elastic pools using the vCore purchasing model
- 有关弹性池的 DTU 资源限制，请参阅使用 DTU 购买模型的弹性池的资源限制For DTU resource limits for elastic pools, see resource limits for elastic pools using the DTU purchasing model
- 有关 Azure SQL 托管实例中的托管实例的资源限制，请参阅 SQL 托管实例资源限制。For resource limits for managed instances in Azure SQL Managed Instance, see SQL Managed Instance resource limits.
- 有关常规 Azure 限制的相关信息，请参阅 Azure 订阅和服务限制、配额和约束。For information about general Azure limits, see Azure subscription and service limits, quotas, and constraints.
- 有关逻辑 SQL 服务器上的资源限制的信息，请参阅逻辑 SQL 服务器资源限制概述了解有关服务器级别和订阅级别限制的信息。For information about resource limits on a logical SQL server, see overview of resource limits on a logical SQL server for information about limits at the server and subscription levels.