Forum Discussion
zaza
5 years agoResolver III
Optimizing DAX Measure
I have the following measure whihc works perfectly. However my dataset grew from 2 million rows to 42 million rows and Now this measure takes way too much to load, sometimes some visuals where this i...
Anonymous
5 years agoNot applicable
The advice is this: if your fact table is big, then instead of SUMMARIZE (that has to scan the fact table) try to use CROSSJOIN. If the number of combinations you have under your SUMMARIZE is decent (relatively low), this should give you a faster measure. But it all depends on your data distribution. CROSSJOIN does not have to scan the whole fact table, only the relevant (small) dimensions.