Forum Discussion

karthik77700's avatar
karthik77700
Helper I
2 years ago
Solved

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?

 

 

Need Help

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    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.

  • karthik77700's avatar
    karthik77700
    Helper I
    2 years ago

    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