Forum Discussion
Refreshes from SQL over the Gateway taking longer and longer
For cases like this, you have to ask yourself, "What changed?" Some thoughts to get you started:
- Amount of data?
- Power Query steps such that it no longer 'folds'? (Meaning it has to do some steps at the client level, not the SQL Server)
- SQL Indexing strategy?
- Network bandwidth?
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?
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 TeamWe'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.
