Forum Discussion
Queries related to data size in Power Query Editor
- 1 year ago
Thankyou, jennratten, karansingla0311, for your response.
Hi coolsandeee,We appreciate your inquiry on the Microsoft Fabric Community Forum.
Based on my understanding, Power Query Editor does not have a fixed row limit. The limit depends on the available system memory (RAM) and whether you are using a 64-bit or 32-bit version. For Power BI Desktop and On-Premises Data Gateway, the data size you can load and process depends on the RAM and available virtual memory on your machine.
The error message, "Evaluation ran out of memory and can't continue," indicates that the transformation—particularly the unpivot operation—exceeded the available memory during refresh. This is more likely to occur with large datasets (for example, 1 million rows) and when multiple refreshes run in parallel on a gateway machine with 16 GB RAM.
Kindly follow the steps below, which may help resolve the issue:
- Optimize query steps by moving memory-intensive operations such as unpivoting upstream (at the source system or Power BI Dataflows). Reduce the dataset size before applying transformations by filtering or removing unnecessary columns.
- Avoid running multiple heavy refreshes simultaneously on the same gateway.
- Use Performance Monitor to check memory and CPU usage during refresh.
- Consider increasing the Gateway RAM to 32 GB or more if you frequently run concurrent heavy refreshes.
If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar issues.
Thank you.
There are a lot of factors here as well - for example, is your gateway on a machine dedicated to gateway jobs? Were any other refreshes running at the same time? Generally speaking, a million records should not use all the memory. Unpivots are a memory intensive operation, but if you are also seeing this error with only 5k records, I would think there may be a combination of lack of resources and query optimizations needed. Can you tell me more?
There is a dedicated machine for these refreshes. It has a 4 core, 16 GB RAM.
There were 2-3 other report refreshes running along with this failed one.
The error occurred only for a million records and not for the 5K one.