This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
I'm using the Log Analytics integration with my Power BI workspaces to monitor model refreshes. I'm also using the report templates available in Git. I'm seeing an intermittent issue where it takes my model hours to refresh when the typical refresh time is about 20 minutes. Using the reports, I have identified a pattern in which there ExecuteSQL (OperationDetail) takes a few minutes but is then followed by a very long ReadData - sometimes hours.
What I'm trying to determine is, what is "ReadData" and where is it happening? This particular table is being refreshed via a Power BI Gateway so I want to know if ReadData spans the Microsoft service/network, internet, and my on-prem network or if this operation is confined to a subset of those. Is it a Microsoft issue, an internal network issue, or an issue with connectivity between the two.
Any thoughts??
Have you considered using Phil Seamark's approach to real time refresh monitoring?
Thanks. I came across it but I don't need that at this point. I have identified that the issue is with the ReadData operation. Now I just need to understand what that is. Seeing ReadData in real-time wouldn't help me there.
Check out the April 2026 Power BI update to learn about new features.
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.
| User | Count |
|---|---|
| 11 | |
| 9 | |
| 8 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 49 | |
| 32 | |
| 27 | |
| 21 | |
| 20 |