Skip to content

Latest commit

 

History

History
100 lines (78 loc) · 7.9 KB

File metadata and controls

100 lines (78 loc) · 7.9 KB
title Include file
description Include file
author jonburchel
ms.service azure-synapse-analytics
ms.topic include
ms.date 02/20/2025
ms.author jburchel
ms.custom include file

Azure Synapse Analytics has the following default limits to ensure customer's subscriptions are protected from each other's workloads. To raise the limits to the maximum for your subscription, contact support.

Azure Synapse limits for workspaces

For Pay-As-You-Go, Free Trial, Azure Pass, and Azure for Students subscription offer types:

Resource Default limit Maximum limit
Synapse workspaces in an Azure subscription 2 2

For other subscription offer types:

Resource Default limit Maximum limit
Synapse workspaces in an Azure subscription per region 20 100

Azure Synapse limits for Apache Spark

For Pay-As-You-Go, Free Trial, Azure Pass, and Azure for Students subscription offer types:

Resource Memory Optimized cores GPU cores
Spark cores in a Synapse workspace 12 48

For other subscription offer types:

Resource Memory Optimized cores GPU cores
Spark cores in a Synapse workspace 50 50

For additional limits for Spark pools, see Concurrency and API rate limits for Apache Spark pools in Azure Synapse Analytics.

Azure Synapse limits for pipelines

Resource Default limit Maximum limit
Synapse pipelines in a Synapse workspace 800 800
Total number of entities, such as pipelines, data sets, triggers, linked services, Private Endpoints, and integration runtimes, within a workspace 5,000 5,000
Total CPU cores for Azure-SSIS Integration Runtimes under one workspace 256 Find out how to request a quota increase from support.
Concurrent pipeline runs per workspace that's shared among all pipelines in the workspace 10,000 10,000
Concurrent External activity runs per workspace per Azure Integration Runtime region
External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, HDInsight, Web, and others. This limit doesn't apply to Self-hosted IR.
3,000 3,000
Concurrent Pipeline activity runs per workspace per Azure Integration Runtime region
Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete. This limit doesn't apply to Self-hosted IR.
1,000 1,000
Concurrent authoring operations per workspace per Azure Integration Runtime region
Including test connection, browse folder list and table list, preview data. This limit doesn't apply to Self-hosted IR.
200 200
Concurrent Data Integration Units1 consumption per workspace per Azure Integration Runtime region Region group 12: 6,000
Region group 22: 3,000
Region group 32: 1,500
Managed virtual network2: 2,0
Region group 12: 6,000
Region group 22: 3,000
Region group 32: 1,500
Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region in managed virtual network 2,0 2,0
Maximum activities per pipeline, which includes inner activities for containers 120 120
Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime 100 100
Maximum parameters per pipeline 50 50
ForEach items 100,000 100,000
ForEach parallelism 20 50
Maximum queued runs per pipeline 100 100
Characters per expression 8,192 8,192
Minimum tumbling window trigger interval 5 min 15 min
Maximum timeout for pipeline activity runs 7 days 7 days
Bytes per object for pipeline objects3 200 KB 200 KB
Bytes per object for dataset and linked service objects3 100 KB 2,000 KB
Bytes per payload for each activity run4 896 KB 896 KB
Data Integration Units1 per copy activity run 256 256
Write API calls 1,200/h 1,200/h

This limit is imposed by Azure Resource Manager, not Azure Synapse Analytics.
Read API calls 12,500/h 12,500/h

This limit is imposed by Azure Resource Manager, not Azure Synapse Analytics.
Monitoring queries per minute 1,000 1,000
Maximum time of data flow debug session 8 hrs 8 hrs
Concurrent number of data flows per integration runtime 50 50
Concurrent number of data flows per integration runtime in managed vNet 20 20
Concurrent number of data flow debug sessions per user per workspace 3 3
Data Flow Azure IR TTL limit 4 hrs 4 hrs
Meta Data Entity Size limit in a workspace 2 GB 2 GB

1 The data integration unit (DIU) is used in a cloud-to-cloud copy operation, learn more from Data integration units (version 2). For information on billing, see Azure Synapse Analytics Pricing.

2 Azure Integration Runtime is globally available to ensure data compliance, efficiency, and reduced network egress costs.

Region group Regions
Region group 1 Central US, East US, East US 2, North Europe, West Europe, West US, West US 2
Region group 2 Australia East, Australia Southeast, Brazil South, Central India, Japan East, North Central US, South Central US, Southeast Asia, West Central US
Region group 3 Other regions

If managed virtual network is enabled, the data integration unit (DIU) in all region groups are 2,400.

3 Pipeline, data set, and linked service objects represent a logical grouping of your workload. Limits for these objects don't relate to the amount of data you can move and process with Azure Synapse Analytics. Synapse Analytics is designed to scale to handle petabytes of data.

4 The payload for each activity run includes the activity configuration, the associated dataset(s), and linked service(s) configurations if any, and a small portion of system properties generated per activity type. Limit for this payload size doesn't relate to the amount of data you can move and process with Azure Synapse Analytics. Learn about the symptoms and recommendation if you hit this limit.

Azure Synapse limits for dedicated SQL pools

For details of capacity limits for dedicated SQL pools in Azure Synapse Analytics, see dedicated SQL pool resource limits.

Azure Resource Manager limits for web service calls

Azure Resource Manager has limits for API calls. You can make API calls at a rate within the Azure Resource Manager API limits.