使用 DTU 購買模型的彈性集區資源限制Resources limits for elastic pools using the DTU purchasing model

適用於: 是Azure SQL DatabaseAPPLIES TO: yesAzure SQL Database

本文針對使用 DTU 購買模型的彈性集區中的 Azure SQL Database,提供資料庫的詳細資源限制。This article provides the detailed resource limits for databases in Azure SQL Database that are within an elastic pool using the DTU purchasing model.

彈性集區:儲存體大小與計算大小Elastic pool: Storage sizes and compute sizes

針對 Azure SQL Database 彈性集區,下表顯示每個服務層級和計算大小的可用資源。For Azure SQL Database elastic pools, the following tables show the resources available at each service tier and compute size. 您可以使用下列內容來設定服務層、計算大小和儲存體數量:You can set the service tier, compute size, and storage amount using:

重要

如需調整指引和考慮,請參閱調整彈性集For scaling guidance and considerations, see Scale an elastic pool

根據 DTU 和服務層級,彈性集區中個別資料庫的資源限制通常與集區外部之單一資料庫的資源限制相同。The resource limits of individual databases in elastic pools are generally the same as for single databases outside of pools based on DTUs and the service tier. 例如,S2 資料庫的並行背景工作數上限是 120 個背景工作。For example, the max concurrent workers for an S2 database is 120 workers. 因此,如果集區中每個資料庫的最大 DTU 是 50 DTU (這相當於 S2),標準集區中的資料庫最大並行背景工作數上限也會是 120 個背景工作。So, the max concurrent workers for a database in a Standard pool is also 120 workers if the max DTU per database in the pool is 50 DTUs (which is equivalent to S2).

針對相同數量的 Dtu,提供給彈性集區的資源可能會超過彈性集區以外的單一資料庫所提供的資源。For the same number of DTUs, resources provided to an elastic pool may exceed the resources provided to a single database outside of an elastic pool. 這表示,彈性集區的 eDTU 使用率可能小於集區內各個資料庫的 DTU 使用率總和,視工作負載模式而定。This means it is possible for the eDTU utilization of an elastic pool to be less than the summation of DTU utilization across databases within the pool, depending on workload patterns. 例如,在有一個彈性集區中只有一個資料庫的資料庫 DTU 使用率為100% 的極端案例中,特定工作負載模式的集區 eDTU 使用率可能會是50%。For example, in an extreme case with only one database in an elastic pool where database DTU utilization is 100%, it is possible for pool eDTU utilization to be 50% for certain workload patterns. 即使每個資料庫的最大 DTU 維持在指定集區大小的支援值上限時,也可能會發生這種情況。This can happen even if max DTU per database remains at the maximum supported value for the given pool size.

注意

下表中每個集區資源限制的儲存體不包含 tempdb 和記錄儲存體。The storage per pool resource limit in each of the following tables do not include tempdb and log storage.

基本彈性集區限制Basic elastic pool limits

每集區 eDTUeDTUs per pool 5050 100100 200200 300300 400400 800800 12001200 16001600
每個集區內含的儲存體 (GB)Included storage per pool (GB) 55 1010 2020 2929 3939 7878 117117 156156
每集區最大儲存體 (GB)Max storage per pool (GB) 55 1010 2020 2929 3939 7878 117117 156156
每個集區的記憶體內部 OLTP 儲存體上限 (GB)Max In-Memory OLTP storage per pool (GB) N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A
每個集區的資料庫數目上限1Max number DBs per pool 1 100100 200200 500500 500500 500500 500500 500500 500500
每個集區的最大並行背景工作(要求) 2Max concurrent workers (requests) per pool 2 100100 200200 400400 600600 800800 16001600 24002400 32003200
每個集區的並行會話數上限2Max concurrent sessions per pool 2 3000030000 3000030000 3000030000 3000030000 3000030000 3000030000 3000030000 3000030000
每個資料庫選項的最小 DTU 數Min DTU per database choices 0, 50, 5 0, 50, 5 0, 50, 5 0, 50, 5 0, 50, 5 0, 50, 5 0, 50, 5 0, 50, 5
每個資料庫選擇的最大 DTUMax DTU per database choices 55 55 55 55 55 55 55 55
每個資料庫的儲存體上限 (GB)Max storage per database (GB) 22 22 22 22 22 22 22 22

1如需其他考慮,請參閱密集彈性集區中的資源管理1 See Resource management in dense elastic pools for additional considerations.

2針對任何個別資料庫的最大並行背景工作角色(要求),請參閱單一資料庫資源限制2 For the max concurrent workers (requests) for any individual database, see Single database resource limits. 例如,如果彈性集區使用第5代,而每個資料庫的最大 vCore 設定為2,則並行背景工作角色的最大值為200。For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200. 如果 [每個資料庫的最大 vCore] 設定為0.5,則「並行背景工作角色」的最大值為50,因為在第5代上,每個 vCore 的並行背景工作數上限為100。If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. 對於少於 1 個 V 核心的每個資料庫 V 核心最大數量的其他設定,並行背景工作角色的最大數目也是同樣地重新調整。For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.

標準彈性集區限制Standard elastic pool limits

每集區 eDTUeDTUs per pool 5050 100100 200200 300300 400400 800800
每集區包含的儲存空間(GB) 1Included storage per pool (GB) 1 5050 100100 200200 300300 400400 800800
每集區最大儲存體 (GB)Max storage per pool (GB) 500500 750750 10241024 12801280 15361536 20482048
每個集區的記憶體內部 OLTP 儲存體上限 (GB)Max In-Memory OLTP storage per pool (GB) N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A
每個集區的資料庫數目上限2Max number DBs per pool 2 100100 200200 500500 500500 500500 500500
每個集區的並行背景工作(要求)數上限3Max concurrent workers (requests) per pool 3 100100 200200 400400 600600 800800 16001600
每個集區的並行會話數上限3Max concurrent sessions per pool 3 3000030000 3000030000 3000030000 3000030000 3000030000 3000030000
每個資料庫選項的最小 DTU 數Min DTU per database choices 0, 10, 20, 500, 10, 20, 50 0、10、20、50、1000, 10, 20, 50, 100 0, 10, 20, 50, 100, 2000, 10, 20, 50, 100, 200 0, 10, 20, 50, 100, 200, 3000, 10, 20, 50, 100, 200, 300 0, 10, 20, 50, 100, 200, 300, 4000, 10, 20, 50, 100, 200, 300, 400 0, 10, 20, 50, 100, 200, 300, 400, 8000, 10, 20, 50, 100, 200, 300, 400, 800
每個資料庫選擇的最大 DTUMax DTU per database choices 10, 20, 5010, 20, 50 10、20、50、10010, 20, 50, 100 10, 20, 50, 100, 20010, 20, 50, 100, 200 10, 20, 50, 100, 200, 30010, 20, 50, 100, 200, 300 10, 20, 50, 100, 200, 300, 40010, 20, 50, 100, 200, 300, 400 10, 20, 50, 100, 200, 300, 400, 80010, 20, 50, 100, 200, 300, 400, 800
每個資料庫的儲存體上限 (GB)Max storage per database (GB) 500500 750750 10241024 10241024 10241024 10241024

1如需因布建任何額外的儲存體而產生的額外成本詳細資料,請參閱SQL Database 定價選項1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.

2如需其他考慮,請參閱密集彈性集區中的資源管理2 See Resource management in dense elastic pools for additional considerations.

3針對任何個別資料庫的最大並行背景工作角色(要求),請參閱單一資料庫資源限制3 For the max concurrent workers (requests) for any individual database, see Single database resource limits. 例如,如果彈性集區使用第5代,而每個資料庫的最大 vCore 設定為2,則並行背景工作角色的最大值為200。For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200. 如果 [每個資料庫的最大 vCore] 設定為0.5,則「並行背景工作角色」的最大值為50,因為在第5代上,每個 vCore 的並行背景工作數上限為100。If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. 對於少於 1 個 V 核心的每個資料庫 V 核心最大數量的其他設定,並行背景工作角色的最大數目也是同樣地重新調整。For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.

標準彈性集區限制 (續)Standard elastic pool limits (continued)

每集區 eDTUeDTUs per pool 12001200 16001600 20002000 25002500 30003000
每集區包含的儲存空間(GB) 1Included storage per pool (GB) 1 12001200 16001600 20002000 25002500 30003000
每集區最大儲存體 (GB)Max storage per pool (GB) 25602560 30723072 35843584 40964096 40964096
每個集區的記憶體內部 OLTP 儲存體上限 (GB)Max In-Memory OLTP storage per pool (GB) N/AN/A N/AN/A N/AN/A N/AN/A N/AN/A
每個集區的資料庫數目上限2Max number DBs per pool 2 500500 500500 500500 500500 500500
每個集區的並行背景工作(要求)數上限3Max concurrent workers (requests) per pool 3 24002400 32003200 40004000 50005000 60006000
每個集區的並行會話數上限3Max concurrent sessions per pool 3 3000030000 3000030000 3000030000 3000030000 3000030000
每個資料庫選項的最小 DTU 數Min DTU per database choices 0, 10, 20, 50, 100, 200, 300, 400, 800, 12000, 10, 20, 50, 100, 200, 300, 400, 800, 1200 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 16000, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 20000, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 25000, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500 0, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500, 30000, 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500, 3000
每個資料庫選擇的最大 DTUMax DTU per database choices 10, 20, 50, 100, 200, 300, 400, 800, 120010, 20, 50, 100, 200, 300, 400, 800, 1200 10, 20, 50, 100, 200, 300, 400, 800, 1200, 160010, 20, 50, 100, 200, 300, 400, 800, 1200, 1600 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 200010, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 250010, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500 10, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500, 300010, 20, 50, 100, 200, 300, 400, 800, 1200, 1600, 2000, 2500, 3000
每個資料庫的儲存體上限 (GB)Max storage per database (GB) 10241024 10241024 10241024 10241024 10241024

1如需因布建任何額外的儲存體而產生的額外成本詳細資料,請參閱SQL Database 定價選項1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.

2如需其他考慮,請參閱密集彈性集區中的資源管理2 See Resource management in dense elastic pools for additional considerations.

3針對任何個別資料庫的最大並行背景工作角色(要求),請參閱單一資料庫資源限制3 For the max concurrent workers (requests) for any individual database, see Single database resource limits. 例如,如果彈性集區使用第5代,而每個資料庫的最大 vCore 設定為2,則並行背景工作角色的最大值為200。For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200. 如果 [每個資料庫的最大 vCore] 設定為0.5,則「並行背景工作角色」的最大值為50,因為在第5代上,每個 vCore 的並行背景工作數上限為100。If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. 對於少於 1 個 V 核心的每個資料庫 V 核心最大數量的其他設定,並行背景工作角色的最大數目也是同樣地重新調整。For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.

高階彈性集區限制Premium elastic pool limits

每集區 eDTUeDTUs per pool 125125 250250 500500 10001000 15001500
每集區包含的儲存空間(GB) 1Included storage per pool (GB) 1 250250 500500 750750 10241024 15361536
每集區最大儲存體 (GB)Max storage per pool (GB) 10241024 10241024 10241024 10241024 15361536
每個集區的記憶體內部 OLTP 儲存體上限 (GB)Max In-Memory OLTP storage per pool (GB) 11 22 44 1010 1212
每個集區的資料庫數目上限2Max number DBs per pool 2 5050 100100 100100 100100 100100
每個集區的並行背景工作數上限(要求) 3Max concurrent workers per pool (requests) 3 200200 400400 800800 16001600 24002400
每個集區的並行會話數上限3Max concurrent sessions per pool 3 3000030000 3000030000 3000030000 3000030000 3000030000
每資料庫的 eDTU 下限Min eDTUs per database 0, 25, 50, 75, 1250, 25, 50, 75, 125 0, 25, 50, 75, 125, 2500, 25, 50, 75, 125, 250 0, 25, 50, 75, 125, 250, 5000, 25, 50, 75, 125, 250, 500 0, 25, 50, 75, 125, 250, 500, 10000, 25, 50, 75, 125, 250, 500, 1000 0, 25, 50, 75, 125, 250, 500, 10000, 25, 50, 75, 125, 250, 500, 1000
每資料庫的 eDTU 上限Max eDTUs per database 25, 50, 75, 12525, 50, 75, 125 25, 50, 75, 125, 25025, 50, 75, 125, 250 25, 50, 75, 125, 250, 50025, 50, 75, 125, 250, 500 25, 50, 75, 125, 250, 500, 100025, 50, 75, 125, 250, 500, 1000 25, 50, 75, 125, 250, 500, 100025, 50, 75, 125, 250, 500, 1000
每個資料庫的儲存體上限 (GB)Max storage per database (GB) 10241024 10241024 10241024 10241024 10241024

1如需因布建任何額外的儲存體而產生的額外成本詳細資料,請參閱SQL Database 定價選項1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.

2如需其他考慮,請參閱密集彈性集區中的資源管理2 See Resource management in dense elastic pools for additional considerations.

3針對任何個別資料庫的最大並行背景工作角色(要求),請參閱單一資料庫資源限制3 For the max concurrent workers (requests) for any individual database, see Single database resource limits. 例如,如果彈性集區使用第5代,而每個資料庫的最大 vCore 設定為2,則並行背景工作角色的最大值為200。For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200. 如果 [每個資料庫的最大 vCore] 設定為0.5,則「並行背景工作角色」的最大值為50,因為在第5代上,每個 vCore 的並行背景工作數上限為100。If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. 對於少於 1 個 V 核心的每個資料庫 V 核心最大數量的其他設定,並行背景工作角色的最大數目也是同樣地重新調整。For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.

高階彈性集區限制 (續)Premium elastic pool limits (continued)

每集區 eDTUeDTUs per pool 20002000 25002500 30003000 35003500 40004000
每集區包含的儲存空間(GB) 1Included storage per pool (GB) 1 20482048 25602560 30723072 35483548 40964096
每集區最大儲存體 (GB)Max storage per pool (GB) 20482048 25602560 30723072 35483548 40964096
每個集區的記憶體內部 OLTP 儲存體上限 (GB)Max In-Memory OLTP storage per pool (GB) 1616 2020 2424 2828 3232
每個集區的資料庫數目上限2Max number DBs per pool 2 100100 100100 100100 100100 100100
每個集區的並行背景工作(要求)數上限3Max concurrent workers (requests) per pool 3 32003200 40004000 48004800 56005600 64006400
每個集區的並行會話數上限3Max concurrent sessions per pool 3 3000030000 3000030000 3000030000 3000030000 3000030000
每個資料庫選項的最小 DTU 數Min DTU per database choices 0, 25, 50, 75, 125, 250, 500, 1000, 17500, 25, 50, 75, 125, 250, 500, 1000, 1750 0, 25, 50, 75, 125, 250, 500, 1000, 17500, 25, 50, 75, 125, 250, 500, 1000, 1750 0, 25, 50, 75, 125, 250, 500, 1000, 17500, 25, 50, 75, 125, 250, 500, 1000, 1750 0, 25, 50, 75, 125, 250, 500, 1000, 17500, 25, 50, 75, 125, 250, 500, 1000, 1750 0, 25, 50, 75, 125, 250, 500, 1000, 1750, 40000, 25, 50, 75, 125, 250, 500, 1000, 1750, 4000
每個資料庫選擇的最大 DTUMax DTU per database choices 25, 50, 75, 125, 250, 500, 1000, 175025, 50, 75, 125, 250, 500, 1000, 1750 25, 50, 75, 125, 250, 500, 1000, 175025, 50, 75, 125, 250, 500, 1000, 1750 25, 50, 75, 125, 250, 500, 1000, 175025, 50, 75, 125, 250, 500, 1000, 1750 25, 50, 75, 125, 250, 500, 1000, 175025, 50, 75, 125, 250, 500, 1000, 1750 25, 50, 75, 125, 250, 500, 1000, 1750, 400025, 50, 75, 125, 250, 500, 1000, 1750, 4000
每個資料庫的儲存體上限 (GB)Max storage per database (GB) 10241024 10241024 10241024 10241024 10241024

1如需因布建任何額外的儲存體而產生的額外成本詳細資料,請參閱SQL Database 定價選項1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.

2如需其他考慮,請參閱密集彈性集區中的資源管理2 See Resource management in dense elastic pools for additional considerations.

3針對任何個別資料庫的最大並行背景工作角色(要求),請參閱單一資料庫資源限制3 For the max concurrent workers (requests) for any individual database, see Single database resource limits. 例如,如果彈性集區使用第5代,而每個資料庫的最大 vCore 設定為2,則並行背景工作角色的最大值為200。For example, if the elastic pool is using Gen5 and the max vCore per database is set at 2, then the max concurrent workers value is 200. 如果 [每個資料庫的最大 vCore] 設定為0.5,則「並行背景工作角色」的最大值為50,因為在第5代上,每個 vCore 的並行背景工作數上限為100。If max vCore per database is set to 0.5, then the max concurrent workers value is 50 since on Gen5 there are a max of 100 concurrent workers per vCore. 對於少於 1 個 V 核心的每個資料庫 V 核心最大數量的其他設定,並行背景工作角色的最大數目也是同樣地重新調整。For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.

重要

所有區域目前均可取得進階層中超過 1 TB 的儲存空間,但不包括:中國東部、中國北部、德國中部和德國東北部。More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, and Germany Northeast. 在這些區域中,進階層中的儲存空間上限為 1 TB。In these regions, the storage max in the Premium tier is limited to 1 TB. 如需詳細資訊,請參閱 P11-P15 目前的限制For more information, see P11-P15 current limitations.

如果彈性集區的所有 DTU 均已使用,則集區中的每個資料庫會收到等量的資源以處理查詢。If all DTUs of an elastic pool are used, then each database in the pool receives an equal amount of resources to process queries. SQL Database 服務藉由確保運算時間的均等配量,提供資料庫之間的資源共用公平性。The SQL Database service provides resource sharing fairness between databases by ensuring equal slices of compute time. 彈性集區資源共用公平性不包括任何資源數量,否則當每個資料庫的最小 DTU 數設為非零的值時,便會對每個資料庫保證資源數量。Elastic pool resource sharing fairness is in addition to any amount of resource otherwise guaranteed to each database when the DTU min per database is set to a non-zero value.

注意

如需 tempdb 限制,請參閱tempdb 限制For tempdb limits, see tempdb limits.

集區資料庫的資料庫屬性Database properties for pooled databases

下表描述集區資料庫的屬性。The following table describes the properties for pooled databases.

屬性Property 說明Description
每資料庫的 eDTU 上限Max eDTUs per database 集區中任何資料庫可以使用的 eDTU 數目上限,是否可用則是根據集區中其他資料庫的使用量而定。The maximum number of eDTUs that any database in the pool may use, if available based on utilization by other databases in the pool. 每個資料庫的 eDTU 數目上限不等於資料庫的資源保證。Max eDTU per database is not a resource guarantee for a database. 這個設定是全域設定,會套用至集區中的所有資料庫。This setting is a global setting that applies to all databases in the pool. 將每個資料庫的 eDTU 設定為最上限,以處理資料庫使用率的尖峰。Set max eDTUs per database high enough to handle peaks in database utilization. 某種程度的過量使用是可預期的情況,因為集區通常會假設資料庫的熱門和冷門使用模式;在這些模式中,所有資料庫不會同時處於尖峰期。Some degree of overcommitting is expected since the pool generally assumes hot and cold usage patterns for databases where all databases are not simultaneously peaking. 例如,假設每個資料庫的尖峰使用量是 20 個 DTU,且集區中的 100 個資料庫只有 20% 會同時暴增到尖峰。For example, suppose the peak utilization per database is 20 eDTUs and only 20% of the 100 databases in the pool are peak at the same time. 如果每一資料庫的 eDTU 上限設為 20 個 eDTU,則以 5 倍的量過量使用集區,並將每集區 eDTU 設為 400 個是合理的作法。If the eDTU max per database is set to 20 eDTUs, then it is reasonable to overcommit the pool by 5 times, and set the eDTUs per pool to 400.
每資料庫的 eDTU 下限Min eDTUs per database 集區中單一資料庫能夠保證的最小 eDTU 數。The minimum number of eDTUs that any database in the pool is guaranteed. 這個設定是全域設定,會套用至集區中的所有資料庫。This setting is a global setting that applies to all databases in the pool. 每個資料庫最小 eDTU 建議設定為 0,同時也是預設值。The min eDTU per database may be set to 0, and is also the default value. 此屬性會設為 0 到每一資料庫的 eDTU 使用量平均值之間的任意數。This property is set to anywhere between 0 and the average eDTU utilization per database. 集區中資料庫數目和每個資料庫 eDTU 數目下限的乘積不能超過每個集區的 eDTU。The product of the number of databases in the pool and the min eDTUs per database cannot exceed the eDTUs per pool. 例如,如果集區有 20 個資料庫,且每個資料庫的最小 eDTU 設定為 10 eDTU,則每個集區 eDTU 必須至少為 200 個 eDTU。For example, if a pool has 20 databases and the eDTU min per database set to 10 eDTUs, then the eDTUs per pool must be at least as large as 200 eDTUs.
每個資料庫的儲存體上限Max storage per database 使用者所設定集區資料庫的資料庫大小上限。The maximum database size set by the user for a database in a pool. 不過,集區資料庫會共用配置的集區儲存體。However, pooled databases share allocated pool storage. 即使每個資料庫的儲存體上限設定為大於集區的可用儲存空間總計,但所有資料庫實際使用的總空間將無法超過可用的集區限制。Even if the total max storage per database is set to be greater than the total available storage space of the pool, the total space actually used by all of the databases will not be able to exceed the available pool limit. 資料庫大小上限是指資料檔案的大小上限,並不包含記錄檔所使用的空間。Max database size refers to the maximum size of the data files and does not include the space used by log files.

後續步驟Next steps