Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
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.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
143 | |
80 | |
65 | |
52 | |
49 |
User | Count |
---|---|
212 | |
89 | |
79 | |
68 | |
60 |