Forum Discussion
Strategies to reduce paginated report initial load time?
- 1 year ago
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.
Did you examine the queries that run against your database? Are these queries covered by indexes and up to date statistics?
- MarkPalmberg1 year ago
Kudo Commander
We continue to poke at this issue. An extremely common reporting scenario around here (and all over, I presume) is to have a stored proc that returns a list of financial transactions by transaction date and a hierarchy of designation "levels," like College, Department, Area. So we need datasets in the RDL for the designation level values to souce those parameter values, and they're dependent on each other (Department looks up to College; Area looks up to Department). I guess right now we're at the stage where we're experimenting to find the fastest way to run these parameter datasets.