We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
I created "QueryZ" (using Append) that establishes a population of accounts coming from 2 tables. I want to use those accounts as a filter against other tables. So I do a Table.Join against some table (call it TableX) hoping the load process will only scan a limited number of rows from TableX. However, Power BI still seems to try to scan the entirety of TableX during the load process. Is there a best practice of how to do mergeing in Power Query (or otherwise leveraging the accounts from Query1) to prevent the load process from scanning the full TableX.
This issue is important to me because I happen to be dealing with massive tables so I need the tool to not evaluate excess rows unneccesarily.
You might experience this bug in query folding: http://www.thebiccountant.com/2017/07/20/sql-query-folding-bug-still-alive-sucking-powerbi-powerquer...
Imke Feldmann (The BIccountant)
If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!
How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries
There are some tips on this page.
https://exceleratorbi.com.au/best-practices-power-pivot-power-query-power-bi/
Also you can turn on tracing from the setting menu which may help you see what it's doing and if any changes are making it better or worse.
There are some buffer functions that may help.
Some posts that may have useful details
http://community.powerbi.com/t5/Desktop/merging-tables-very-slow-performance/td-p/122730
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 |
|---|---|
| 53 | |
| 38 | |
| 33 | |
| 17 | |
| 17 |
| User | Count |
|---|---|
| 67 | |
| 63 | |
| 38 | |
| 34 | |
| 22 |