Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
karthik77700
Helper I
Helper I

Report -Resource governing error

When i run the report throwing below error:

We are able to load three months of data when trying to load fourth month we are getting above error.We have P2 Premium capacity which is dedicated to only one workspace and it is not shared to anyother workspace.

Since it is insurance data data volume is huge only.Moving to Premium P3 is more costly ,currently our requirement is to show four months of data only .

Data model is star schema and we have moved all calculated columns to dataflow level which is the source of the report .

And we have tried to load incremental refresh as well but still its throwing this error.

Any further suggestion to resolve this issue?

karthik77700_0-1712139316898.png

 

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @karthik77700 ,

Please refer this document: Advanced incremental refresh and real-time data with the XMLA endpoint in Power BI - Power BI | Micr...

 

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

3 REPLIES 3
karthik77700
Helper I
Helper I

Thanks but we tried to restrict the data using Incremental refresh as well we have loaded three months of data and it was archieved and when trying to load fourth month as incremental refresh it was failing again.

Can you let us know how to reduce number of partitions in query execution

Anonymous
Not applicable

Hi @karthik77700 ,

Please refer this document: Advanced incremental refresh and real-time data with the XMLA endpoint in Power BI - Power BI | Micr...

 

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous
Not applicable

Hi @karthik77700 ,

This is because command operation attempts to consume more memory than allowed by the limit, the operation fail, and an error is returned.

 

To potentially avoid exceeding the effective memory limit:

  • Upgrade to a larger Premium capacity (SKU) size for the semantic model.
  • Reduce the memory footprint of your semantic model by limiting the amount of data loaded with each refresh.
  • For refresh operations through the XMLA endpoint, reduce the number of partitions being processed in parallel. Too many partitions being processed in parallel with a single command can exceed the effective memory limit.

For more details, you could read related document: Troubleshoot XMLA endpoint connectivity in Power BI - Power BI | Microsoft Learn

 

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.