概觀 Azure SQL Database 受控執行個體的資源限制Overview Azure SQL Database managed instance resource limits

這篇文章提供 Azure SQL Database 受控執行個體的資源限制的概觀,並提供有關如何要求增加這些限制的資訊。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 Database 受控執行個體可以在兩個世代的硬體上部署: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 虛擬核心 = 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,虛擬核心 = 1 LP (超執行緒)Intel E5-2673 v4 (Broadwell) 2.3-GHz processors, fast NVMe SSD, vCore=1 LP (hyper-thread)
虛擬核心vCores 8 個、16 個、24 個虛擬核心8, 16, 24 vCores 4、 8、 16、 24、 32、 40、 64、 80 的 v 核心4, 8, 16, 24, 32, 40, 64, 80 vCores
記憶體 (記憶體/核心比例)Memory (memory/core ratio) 每個虛擬核心 7GB7 GB per vCore 每個虛擬核心 5.1 GB5.1 GB per vCore
最大記憶體內部 OLTP 記憶體Max In-Memory OLTP memory 執行個體限制:每個虛擬核心 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
執行個體限制:每個虛擬核心 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
虛擬核心數目*Number of vCores* 第 4 代:8、16、24Gen4: 8, 16, 24
第 5 代:4, 8, 16, 24, 32, 40, 64, 80Gen5: 4, 8, 16, 24, 32, 40, 64, 80
第 4 代:8、16、24、32Gen4: 8, 16, 24, 32
第 5 代:4, 8, 16, 24, 32, 40, 64, 80Gen5: 4, 8, 16, 24, 32, 40, 64, 80
記憶體Memory 第 4 代:56 GB-168 GB (7 GB/vCore)Gen4: 56 GB - 168 GB (7GB/vCore)
第 5 代:40.8 GB-408 GB (5.1 GB/vCore)Gen5: 40.8 GB - 408 GB (5.1GB/vCore)
第 4 代:56 GB-168 GB (7 GB/vCore)Gen4: 56 GB - 168 GB (7GB/vCore)
第 5 代:40.8 GB-408 GB (5.1 GB/vCore)Gen5: 40.8 GB - 408 GB (5.1GB/vCore)
執行個體儲存體大小上限Max instance storage size -4 個 Vcore (僅第 5 代) 2 TB- 2 TB for 4 vCores (Gen5 only)
如需其他大小的 8 TB- 8 TB for other sizes
第 4 代:1 TBGen4: 1 TB
第 5 代:Gen5:
-1 TB 的 4、 8、 16 個 Vcore- 1 TB for 4, 8, 16 vCores
- 2 TB (適用於 24 個虛擬核心)- 2 TB for 24 vCores
- 4 TB (適用於 32、40、64、80 個虛擬核心)- 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,500500 - 7,500 per file
*視檔案大小而定*Depends on the file size
11 K-110 K (1375年/虛擬核心)11 K - 110 K (1375/vCore)
記錄輸送量Log throughput 每個虛擬核心 3 MB/秒3 MB/s per vCore
最大 22 MB/s 每個執行個體Max 22 MB/s per instance
4 MB/s 每個虛擬核心4 MB/s per vCore
最大 48 MB/s 每個執行個體Max 48 MB/s per instance
資料輸送量 (大約)Data throughput (approximate) 每個檔案 100 - 250 MB/秒100 - 250 MB/s per file
*視檔案大小而定*Depends on the file size
N/AN/A
IO 延遲 (大約)IO latency (approximate) 5-10 毫秒5-10 ms 1-2 毫秒1-2 ms
最大 tempDB 大小Max tempDB size 192 - 1920 GB (每個虛擬核心 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 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 入口網站中的支援要求如果您需要更多目前的區域中的 managed 執行個體。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 區域中建立新的 managed 執行個體而不需要傳送的支援要求。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 單位 * 虛擬核心數目上限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 企業版Visual Studio Enterprise 22 6464
Visual Studio Professional 及 MSDN 平台Visual Studio Professional and MSDN Platforms 22 3232

* 當您計劃您的部署時,請考慮業務關鍵 (BC) vCore (因為已新增備援) 會耗用 4 倍比一般用途 (GP) 虛擬核心的更多容量。* 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. 因此,您的計算,GP 1 個 vCore = 1 個虛擬核心單元測試和 1 BC vCore = 4 個 vCore 的單位。So, for your calculations, 1 GP vCore = 1 vCore unit and 1 BC vCore = 4 vCore units. 若要簡化您耗用量的分析超越預設限制,摘要說明跨所有受管理的執行個體已部署並比較其結果與您的訂用帳戶類型的執行個體單位限制的所在區域中的子網路的虛擬核心單位。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. 虛擬核心單位的最大數目限制會套用至區域中的每個訂用帳戶。Max number of vCore units limit applies to each subscription in a region. 沒有任何限制每個個別的子網路不同之處在於部署跨多個子網路的所有虛擬核心的總和必須是較低或等於虛擬核心單位的數目上限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.

* * 較大子網路和虛擬核心的限制會在以下區域上市:澳大利亞東部、 美國東部、 美國東部 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 Database 受控執行個體] 。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.
      • 所需的每個服務層之後配額的現有子網路中的虛擬核心,數目增加 (如果有任何現有的子網路需要展開。Required number of vCores, per service tier in existing subnets after the quota increase (if any of the existing subnets needs to be expanded.
      • (如果您要部署新的子網路中的 managed 執行個體),需要新的子網路數目和每個新的子網路內的服務層的虛擬核心總數。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