Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
70 | |
68 | |
43 | |
34 | |
26 |
User | Count |
---|---|
86 | |
49 | |
45 | |
38 | |
37 |