Forum Discussion
Query memory limit for XMLA operations
Hi,
Will the setting Query memory limit % or Query timeout be applied to queries generated using XMLA endpoint? Eg queries from excel connected to semantic model?
Hello kamilnoczynski ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution we provided for your issue worked for you or let us know if you need any further assistance?
Your feedback is important to us, Looking forward to your response.
Thank You.
7 Replies
Hi kamilnoczynski Yes, the query memory limit and timeout settings in Power BI Premium apply to XMLA endpoint queries, including those from Excel connected to a semantic model. These settings control memory usage and query duration. Adjust them in the capacity settings as needed.
If this post helped please do give a kudos and accept this as a solution
Thanks In AdvanceHi kamilnoczynski ,
Thank you Akash_Varuna , for your quick response. The Query Memory Limit % and Query Timeout settings in Microsoft Fabric are essential for queries executed via the XMLA endpoint, including those from Excel connected to a Semantic Model. To enhance performance and prevent query failures.
1. Adjust the Query Timeout setting in Power BI Service to permit longer execution times and avoid timeouts.
2. Increase the Query Memory Limit % to allocate more memory resources and prevent failures due to memory constraints.
3. Optimize DAX measures in the Semantic Model to improve query performance.
Implementing these adjustments will optimize query execution and enhance performance when utilizing the XMLA endpoint.
Helpful References :Configure Workloads in Power BI Premium
Semantic Model Connectivity with XMLA EndpointLet me know if you need further refinements.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.Hello kamilnoczynski ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution we provided for your issue worked for you or let us know if you need any further assistance?
Your feedback is important to us, Looking forward to your response.
Thank You.
Hello kamilnoczynski ,
We are following up to see if the solution we provided resolved your issue. If you need further assistance or have any additional questions, please let us know. Your feedback is important to us, and we look forward to your response.
Thank You.
The main issue is that users of Excel connected to the semantic model are consuming a lot of Premium Capacity and we see high peaks in fabric capacity metrics, and there is a need to set a limit for them. Would it be a better idea to change the settings in SSAS at the workspace level as described in this article: https://powerbi.microsoft.com/en-us/blog/analysis-services-server-properties-in-power-bi-premium-are-now-in-public-preview/ ?
Unfortunately it is not possible to do any changes in semantic model
Hi kamilnoczynski ,
Since modifying the semantic model is not feasible, the optimal approach is to manage query memory usage at the workspace level within the Power BI Premium capacity settings.
To prevent Excel users from consuming excessive memory, you can adjust the Query Memory Limit (%) in the Power BI Admin Portal.
While you can’t increase the query memory limit over the published thresholds, capacity admins can reduce the query memory limit in the admin portal by setting the Query Memory Limit % property on the capacity.
The default value of this property is 0, which means the maximum value for the capacity SKU you’re using will be applied; any other value will be interpreted as a percentage of that maximum value
Steps to Apply :
1. Open Power BI Admin Portal and go to Capacity Settings.
2️. Select your Premium Capacity.
3️. Expand Workloads and find Semantic Models.
4️. Set Query Memory Limit (%):- 0% (Default) → Uses the max memory allowed.
- Lower value (e.g., 50%) → Limits memory per query.
5. Click Save to apply changes.
Helpful References: Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn
If my response solved your query, please mark it as the Accepted solution to help others find it easily.
And if my answer was helpful, I'd really appreciate a 'Kudos'.
Hello kamilnoczynski ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
