Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi All,
i need a help for an existing direct query power bi dashboard.
The direct query uses PortfolioCodeParameter as input for the selected PortfolioCode from dashboard and gets the data from a sql.
table.. The total records retrieved once is around 500,000(1/2 million) and there are 10 measures that are being calculated once data is retrieved,
The entire process of completion is taking around 40 seconds.. is there a way to or any settings to improve the performance of this direct query? Please help
[Query="SELECT [Level_Code]#(lf) ,[NODE_NAME]#(lf) ,[HEX_VALUE]#(lf) ,[portfolio_code]#(lf)
,[date_from]#(lf) ,[sequence]#(lf)
,[log_portfolio_base]#(lf) ,[log_contribution_base]#(lf)
FROM [look_through_temp_dashboard]
where portfolio_code='" & PortfolioCodeParameter & "'"]
Solved! Go to Solution.
The total records retrieved once is around 500,000(1/2 million) and there are 10 measures that are being calculated once data is retrieved,
No, not once. EVERY. SINGLE. TIME. a user interacts with the report element that uses that data source.
Note that there is a hard 1M row limit for Direct Query result sets. You are already at half that limit. You will want to consider aggregating your data at the source to drastically reduce the amount of data traveling over the nework for each query.
At a minimum you will want to put an index on portfolio_code and make sure the statistics are kept up to date. However you will also want to examine the actual SQL query and add more indexes accordingly.
The total records retrieved once is around 500,000(1/2 million) and there are 10 measures that are being calculated once data is retrieved,
No, not once. EVERY. SINGLE. TIME. a user interacts with the report element that uses that data source.
Note that there is a hard 1M row limit for Direct Query result sets. You are already at half that limit. You will want to consider aggregating your data at the source to drastically reduce the amount of data traveling over the nework for each query.
At a minimum you will want to put an index on portfolio_code and make sure the statistics are kept up to date. However you will also want to examine the actual SQL query and add more indexes accordingly.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 29 | |
| 27 | |
| 25 | |
| 25 | |
| 18 |
| User | Count |
|---|---|
| 54 | |
| 49 | |
| 43 | |
| 36 | |
| 32 |