Forum Discussion
Kudo CommanderStrategies to reduce paginated report initial load time?
Hi MarkPalmberg
The slow load time of your paginated report in Power BI Service (75 seconds to load parameters) may be due to slow-performing SQL queries in the stored procedure or dynamic parameter queries fetching large datasets. To improve performance, optimize the stored procedure by reviewing indexing and query execution on Azure SQL Server. Limit dynamic parameters or use static pre-populated values to reduce load time. Ensure your Azure SQL Server is using a high-performance tier, and enable data caching in Power BI Premium for quicker report generation. Reducing the number of parameters and checking Power BI's premium capacity settings for potential bottlenecks will also help. Ensure that both Azure SQL Server and Power BI Service are in the same region to minimize network latency. Regularly monitor resource usage with Azure Monitor to detect any issues.
Kudo CommanderThanks, Poojara_D12 , lbendlin and GilbertQ . I just got done re-writing my proc from the ground up. It executes in my test environment in ~8 seconds, which is pretty fast for our test server.
I'm wondering now if what I'm seeing is an issue with our Azure VNet. We're using a data gateway in the service to connect to our Azure SQL servers because we've implemented a VNet, and I guess it's possible that there's some sort of authentication handshake happening there on RDL load that's responsible for the performance hit we're seeing...?
Super UserHi MarkPalmberg
I certainly think going via the vnet gateway definitely adds more complexity and time to get to where it needs to get to. So that could certainly be why it is taking a lot longer to render.