Forum Discussion
rsQueryMemoryLimitExceeded Error in P&L / Balance Sheet Measure (Small Dataset)
- 5 months ago
Hi Raja10ram ,
Thanks for reaching out to Microsoft Fabric Community.
In addition to the suggestion shared by AjiteshChurewal , since the error indicates that the query has reached the configured memory limit, please review the Query Memory Limit setting in the Admin Portal under Capacity settings.
If a specific percentage value is configured, you may reset it to 0 and re test the matrix visual. The default value is 0, which allows the maximum memory available for your current SKU.
You may also review the memory limits applicable to your Fabric or Premium capacity and upgrade your SKU to get higher query memory limit.
How to configure workloads in Power BI Premium - Microsoft Fabric | Microsoft Learn
From a DAX perspective, the large text based SWITCH statement combined with repeated REMOVEFILTERS calls can significantly increase query memory usage, especially in a matrix visual with multiple rows and years. You may consider simplifying the logic, reducing repeated context removal, and validating that the dimension table is properly related to the fact table so that aggregation flows through the model instead of being handled inside a single complex measure.
Please let us know if you need any further assistance.
Thank you.
Hi Raja10ram ,
Thanks for reaching out to Microsoft Fabric Community.
In addition to the suggestion shared by AjiteshChurewal , since the error indicates that the query has reached the configured memory limit, please review the Query Memory Limit setting in the Admin Portal under Capacity settings.
If a specific percentage value is configured, you may reset it to 0 and re test the matrix visual. The default value is 0, which allows the maximum memory available for your current SKU.
You may also review the memory limits applicable to your Fabric or Premium capacity and upgrade your SKU to get higher query memory limit.
How to configure workloads in Power BI Premium - Microsoft Fabric | Microsoft Learn
From a DAX perspective, the large text based SWITCH statement combined with repeated REMOVEFILTERS calls can significantly increase query memory usage, especially in a matrix visual with multiple rows and years. You may consider simplifying the logic, reducing repeated context removal, and validating that the dimension table is properly related to the fact table so that aggregation flows through the model instead of being handled inside a single complex measure.
Please let us know if you need any further assistance.
Thank you.