Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi!
Our datasource is a Orcle database and I am trying to figure out why the first partition never is run with parallelism when refreshing a dataset.
If I run 7 partitions in a table the parallelism looks like this:
The first partition runs on its own then the other 6 in parallelism
If I run 5 partitions in a table the parallelism looks like this:
The first partition runs on its own then the other 4 in parallelism.
Does any one know why not all 5 partitions runs in parallelism in my last run?
Solved! Go to Solution.
Hi @FredrikJ
This is by design because the first query that runs, does the checks to ensure that the columns are valid and that there are no refreshing errors. Once the first query is successful it can then refresh in Parallel knowing that the subsequent queries will not fail.
Hi @FredrikJ
This is by design because the first query that runs, does the checks to ensure that the columns are valid and that there are no refreshing errors. Once the first query is successful it can then refresh in Parallel knowing that the subsequent queries will not fail.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 16 | |
| 13 | |
| 8 | |
| 8 | |
| 5 |
| User | Count |
|---|---|
| 30 | |
| 27 | |
| 25 | |
| 24 | |
| 24 |