There are not enough vcores resources available in the workspace while running the synapse dataflows
Hi Team,
we are getting the below error dataflow while running in for each activity,
Could you please help us to fix this
**There are not enough resources available in the workspace, details: 'Your job requested 8 vcores. However, the workspace only has 4 vcores available out of quota of 60 vcores for node size family [MemoryOptimized]. Try ending the running job(s), reducing the numbers of vcores requested or increasing your vcore quota
**
Other Than this is there any solution to fix that error.
Azure Portal → Synapse Workspace → Usage + quotas. Find your MemoryOptimized quota. Request increase.
I'm not able to see the Usage + quotas option in synapse can you please share the screen where you were seeing.
Thanks in Advance
Thanks
Azure Synapse Analytics
-
Smaran Thoomu • 22,350 Reputation points • Microsoft External Staff
2025-04-15T12:31:33.9366667+00:00 Hi @SaiSekhar, MahasivaRavi (Philadelphia)
The error you're encountering:
"Your job requested 8 vcores. However, the workspace only has 4 vcores available out of quota of 60 vcores for node size family [MemoryOptimized]."
Indicates that there are insufficient available vCores in your Synapse workspace at the time of Data Flow execution, especially when running within a ForEach activity, which may be triggering multiple parallel executions.
Even though your workspace has a 60 vCore quota, at the time your job runs, only 4 vCores are free. This could be due to:
- Other Data Flows or Spark jobs consuming resources.
- Too many parallel executions within the ForEach loop.
- Data Flows using a node size configuration requesting more cores than available.
Suggested solutions:
- Set the
Batch Count
property in the ForEach activity to a lower value (e.g., 2 or 3) to reduce simultaneous executions and resource contention. - In your Data Flow activity, adjust the integration runtime settings to use a smaller compute size (e.g., General Purpose Small or Medium) or lower the core count under Core Count per node.
- Check the Monitor hub for any active or stuck jobs consuming vCores, and cancel them if not needed.
- Although you mentioned not seeing the Usage + quotas section, here's how you can request more vCores:
Steps:
- Go to Azure Portal.
- Open "Subscriptions" > Your Subscription.
- In the left-hand pane, go to "Usage + quotas"
If the adjustable column indicates 'Yes', you can request the adjustment. Otherwise, if it indicates 'No', you should raise a support ticket. Based on the region, you can select where your resources are relying.
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
-
SaiSekhar, MahasivaRavi (Philadelphia) • 140 Reputation points
2025-04-15T14:01:39.86+00:00 Hi @Smaran Thoomu,
Thanks for the update, we will check for the above methods implementation, can you please guide for Usage + quotas In the below screen shot which metrics we have to check. -
Smaran Thoomu • 22,350 Reputation points • Microsoft External Staff
2025-04-16T10:24:13.7966667+00:00 Hi @SaiSekhar, MahasivaRavi (Philadelphia)
You're correct that it can be tricky to find the right vCore metrics, especially if the provider or region filter is not set properly.
Please find below a screenshot for guidance. Here are the key things to note:
- Provider: Make sure it's set to the correct resource type - for Synapse, that would be
Microsoft.Synapse
. - Region: Should match the region where your Synapse workspace is deployed (e.g., East US 2).
- In this screenshot, the example shown is for
Azure PostgreSQL
just as a reference — you should switch to Microsoft.Synapse under the provider filter.
If visible, you can click on the Request adjustment option (top-right) to request a quota increase for vCores.
If you still don’t see the relevant quotas even after applying filters, you may want to raise a support ticket to request the vCore increase for Synapse.
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
- Provider: Make sure it's set to the correct resource type - for Synapse, that would be
-
Smaran Thoomu • 22,350 Reputation points • Microsoft External Staff
2025-04-17T07:51:49.1166667+00:00 @SaiSekhar, MahasivaRavi (Philadelphia) We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
-
SaiSekhar, MahasivaRavi (Philadelphia) • 140 Reputation points
2025-04-17T12:05:06.48+00:00 Hi @Smaran Thoomu,
Thanks for the update, it is already stated as yes, thank you for helping us,
But now we are facing one more issue the record count in delta table 126022273, we have around 5 tables with this count, it is running more than 5 hours how to optimize the performance for this Hugh data in dataflow, can you please share any other options.Thanks in advance
-
Dileep Raj Narayan Thumula • 0 Reputation points • Microsoft External Staff
2025-04-17T13:38:32.3933333+00:00 Hi @SaiSekhar, MahasivaRavi (Philadelphia) The error
"There are not enough resources available in the workspace, details:'Your job requested 8 vcores'"
In Azure Synapse Analytics indicates that the dataflow job is requesting more vCores (virtual CPU cores) than are currently available within the Synapse workspace
The number of vCores depends on the cluster type and size. For example, in the case of Data Flows and Integration Runtime, a "small" cluster typically uses 8 vCores. Synapse supports specific
vCore configurations like 8, 16, 32, 48, 80, 144, and 272.
If you are referring to Azure Synapse in general, each Synapse workspace comes with a default vCore quota. This quota is not publicly disclosed, so if you need an increase, you will have to contact Microsoft Support. The total quota is shared between user activities and dataflows to ensure one doesn't consume all available resources. The exact quota allocation can vary based on your Azure subscription type, but the split between user and dataflow usage is balanced.
A Data Flow activity requires a minimum of 8 vCores to run. So, with a vCore limit of 50 for the workspace
-
SaiSekhar, MahasivaRavi (Philadelphia) • 140 Reputation points
2025-04-17T13:49:01.89+00:00 Hi @Dileep Raj Narayan Thumula,
Thanks for the update,
Now I'm requesting you that, if we have Hugh volume of data like 126022273 rows, we are doing full load, it is taking more than 4 hours, can you please guide us how to handle this scenario in dataflow in synapse. -
Dileep Raj Narayan Thumula • 0 Reputation points • Microsoft External Staff
2025-04-21T10:56:29.9166667+00:00 Hi @ SaiSekhar, MahasivaRavi (Philadelphia)
As you mention that you are dealing with huge volume of data like 126022273 rows, and also you are doing full load, it is taking more than 4 hours,
Consider these If Data Flow Is Necessary
Optimize Source Settings
Enable source pushdown where possible (for SQL, Parquet, etc.).
Read from partitioned sources if available.
Avoid pulling more columns than needed.
Increase Data Flow Debug Cluster Size
Use a larger Integration Runtime (IR):
General-purpose: 32 or 64 cores.
For heavy loads: Use Memory optimized IR.
Set Core count based on data size (e.g., 32–64 cores for 100M+ rows).
Set Data Flow Partitioning
Default partitioning might not be enough.
In source/sink and transformation settings, use:
Hash partitioning on a high-cardinality column (like ID).
Set partition count manually (start with 16–32).
Example:
Partitioning: Hash
Key: [Your Primary Key or High Cardinality Column]
Partitions: 32 (adjust based on performance)
-
Dileep Raj Narayan Thumula • 0 Reputation points • Microsoft External Staff
2025-04-22T11:14:47.7366667+00:00 Hello @SaiSekhar, MahasivaRavi (Philadelphia),
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help. -
SaiSekhar, MahasivaRavi (Philadelphia) • 140 Reputation points
2025-04-22T11:52:11.8933333+00:00 Hi @Dileep Raj Narayan Thumula,
Thanks for the update,
We are using the above approach -
Dileep Raj Narayan Thumula • 0 Reputation points • Microsoft External Staff
2025-04-22T12:30:06.65+00:00 Hi SaiSekhar, MahasivaRavi (Philadelphia)
As you mentioned you are using the same approach.
Did it helped you? were able to fix the issue?Kindly let me know if you have any questions.
-
Dileep Raj Narayan Thumula • 0 Reputation points • Microsoft External Staff
2025-04-23T12:10:58.0166667+00:00 Hello @SaiSekhar, MahasivaRavi (Philadelphia), We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
-
Dileep Raj Narayan Thumula • 0 Reputation points • Microsoft External Staff
2025-04-24T11:52:44.7+00:00 Hello @SaiSekhar, MahasivaRavi (Philadelphia), We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sign in to comment