Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
We have a Power BI Premium Capacity (yep, still thanks to our EA) and I've noticed that over the past year, data refreshes for Power BI reports published to the service are taking an average of 200 seconds longer than they did at the same time last year. I've done some work to try and spread the load out so we don't have so many refreshes happening concurrently, but this still seems like a really big change over the course of one year. Most of our refreshes hit our on-prem SQL datamart, so that means the refreshes use our two-node Power BI gateway setup. The biggest change in refresh times seemed to happen around from September through November 2024, when the average time zoomed up to around 190 seconds. Has anyone else seen anything like this? Has anyone found a solution? Anyone have thoughts as to what might be going on?
For cases like this, you have to ask yourself, "What changed?" Some thoughts to get you started:
Can you isolate the performance issue to one table in a model? What happens if you extract the SQL statement from Power Query and run that against the server directly?
Proud to be a Super User! | |
Appreciate the thoughts. This is across all reports in the tenant and we have over 300. They're all taking much longer to refresh than they did this time last year--from the ones doing the heavy lifting with lots of data, to the ones doing a few dozen rows. The change happened about the same time as we started getting lots of failure for refreshes going across the gateway around July 2024. We then reverted to the May 2024 gateway and didn't update again until October...and that's when we started getting longer and longer refresh times.
One thing to note: we did add the server names to the config file.
https://powerbi.microsoft.com/en-us/blog/on-premises-data-gateway-september-2024-release/
Hi @motoray ,
You saw some relief after rolling back to May 2024, so version differences matter. Try testing with the latest gateway version on a non-production node there may be performance improvements or fixes.
Even small delays between the gateway and your SQL Server can add up across 300+ reports.It’s worth checking for increased network latency or DNS resolution issues
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Menaka.
Community Support Team
We've just installed the May 21, 2025 version recently, but I don't expect that to fix anything. Due to other issues with failed refreshes and open tickets with Microsoft, we've been on the bleeding edge of Gateways since October and refresh times continue to get longer, not shorter.
Hi @motoray
Thanks for the update I completely understand how frustrating this must be, especially after staying up to date with the latest gateway versions and still seeing performance get worse. Since the issue seems persistent across all reports and gateway versions, it may be worth looking into other potential bottlenecks.
Hi @motoray ,
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.
We're currently testing, but still having issues. If we find a solution, I'll come back here and let everyone know. And if someone's suggestion solves the problem, I'll likewise come back and mark that suggestion as the answer. As of right now the problem is still there.
Haven't really made any progress on this still. Testing continues. Long refresh times persist.
Hi @motoray ,
Please go through the below documentation link:
Monitor and optimize on-premises data gateway performance | Microsoft Learn
Best Regards,
Menaka.
Community Support Team
Hi @motoray ,
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
Hi @motoray ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.
Thank you.