Forum Discussion
Optimizing import and refresh
Hi Anonymous
Yes, merging both tables with JoinKind.Inner (instead of the default: LeftOuter) should return the results much faster.
But if you're importing from a foldable source and your Domain tables doesn't come from the same server, you might have to adjust your technique as soon as your Domain-table gets larger than 200 rows: https://www.thebiccountant.com/2017/07/20/sql-query-folding-bug-still-alive-sucking-powerbi-powerquery-excel/
Hi Anonymous
Yes, merging both tables with JoinKind.Inner (instead of the default: LeftOuter) should return the results much faster.
But if you're importing from a foldable source and your Domain tables doesn't come from the same server, you might have to adjust your technique as soon as your Domain-table gets larger than 200 rows: https://www.thebiccountant.com/2017/07/20/sql-query-folding-bug-still-alive-sucking-powerbi-powerquery-excel/
The reason I'm using the Domain table is that I can construct it in such a way that new domains are automatically included.
So far I haven't looked at all into what happens with the folded query, so I will try to study the folded query to see if it is suboptimal.
Hi Anonymous ,
we might have a misunderstanding here.
I'm not recommending against the Domain table.
Just that you should use it differently.
If you use it with the InnerJoin, it will only be adressed once and not per every row of your fact table.