Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
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.
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 8 | |
| 8 | |
| 8 |