Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
We've been experiencing capacity throttling for the past month. Upon analyzing the capacity metrics app, we found that it was caused by a single user on a particular report. However, this report has 7 pages, and the semantic model is an enterprise reporting model with many downstream reports (around 30 odd key reports). Is there a way to identify the specific query that the user is running on the report that's causing the throttling?
PS: We've used the activity logs but couldn't get the query details from them. We can see the report and other details but not the query info.
@lbendlin Can you help with this ?
Hello,rajendraongole1 ,thanks for your concern about this issue.
And I would like to share some additional solutions below.
Hi,@Gow_tham .I am glad to help you.
Based on your description, you currently want to identify the specific query that is causing the capacity limit. And you have already located exactly which report is having the problem.
If your capacity limit issue might be due to the report runtime queries being too large and complex, I hope my suggestions below will help you.
You can try connecting to the report's pbix file using DAX Studio (Power BI Desktop)
Or connect to the semantic model in Power BI Service via XMLA endpoint.
PS: To use XMLA you need to have PPU/Premium capacity licence and above.
URL:
Power BI XMLA Endpoint - Step by Step Examples, How to Use? (excelmojo.com)
DAX Studio captures all DAX queries running on Power BI datasets. This helps identify which queries are consuming the most resources, thus identifying performance bottlenecks.
You can use DAX Studio's Server Timings and Query Plan features to analyse the execution time and resource usage of each query in detail. This helps to understand the specific performance issues in the problematic query.
I hope you find the following article helpful.
URL:
How to Use DAX Studio for Power BI | Hevo
Solved: real size of data model - Microsoft Fabric Community
Getting Connected | DAX Studio
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Gow_tham - can you please check the following solved threads on the same issue.
Solved: Fabric Capacity Metrics - Microsoft Fabric Community
Solved: Fabric Capacity Metrics - Microsoft Fabric Community
Proud to be a Super User! | |
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 31 | |
| 30 | |
| 21 | |
| 16 | |
| 16 |