Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Does anyone have any advice on the best method of ordering query steps to reduce loading time? For example leaving remove duplicates until the last step. Should removing/filtering columns come first?
Any help is appreciated
Solved! Go to Solution.
You may take a look at the post below.
https://community.powerbi.com/t5/Desktop/Query-Folding-Documentation/m-p/359796#M162306
You may take a look at the post below.
https://community.powerbi.com/t5/Desktop/Query-Folding-Documentation/m-p/359796#M162306
In theory, doing your removing/filtering should come first since that reduces the amount of rows/columns that subsequent steps need to process. In theory...
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 63 | |
| 32 | |
| 31 | |
| 25 |