Forum Discussion

thedatahiker's avatar
thedatahiker
Icon for Microsoft Employee rankMicrosoft Employee
4 years ago

Calculate measure in source or in DAX Query

This is a general question that I'm trying to get a clear answer to. If you could provide any documentation that exist on this topic it would be super appreciated.   Is it more performant to calcul...
General Comment
v-yalanwu-msft's avatar
v-yalanwu-msft
Icon for Community Support rankCommunity Support
4 years ago

Hi, thedatahiker ；

My preference is SQL, DAX Measure then DAX calculated column.
1.it can provide better compression if it's a SQL column/expression over a DAX column.
2.SQL is easier to manage change than lots of DAX columns.

3.you can add as a DAX measure then it's not going store any data and calculated when needed.

4.However measure cannot be used for slicers.

 

Best Regards,
Community Support Team_ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

thedatahiker's avatar
thedatahiker
Icon for Microsoft Employee rankMicrosoft Employee
4 years ago

This is closer to the answer I'm hoping to get. You mention that putting the column in the SQL expression can provide better compression and also that by using a DAX measure the value won't be stored in any data and calculated only when needed. Since the DAX measure wouldn't require any storage wouldn't that be a more performant solution? Especially when the fact table can reach into 10s of millions of rows?