cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Power BI Optimization

There is a lot of documentation about when to use DAX Measures vs DAX calculated columns. However, in what instances would it make sense to create a calculated column in the source i.e. SQL vs creating a DAX Measure?

1 ACCEPTED SOLUTION
Applicable88
Impactful Individual
Impactful Individual

@Anonymous,   measures are computed at runtime and calculated columns needs to be stored. That means measures does not need storage space, but the latter do. They also tend to make your calculation slower, since your model grow with the columns generated. Thats the reason when possible to use measures. They are only computed when you need them. Anyway, a good reason for the need of a calculated column might be the need for a "customize" dimension that you need for a bar chart. For example your mastercalendar doesn't consist of a weeknumber to the date, than you need to create one with weeknumber() - function. And now go further that you want to to have a bar chart dimension, where your calendar week is concatenated with the year number together á la " 2021 / 40 " . If you want a customized dimension you need a calculated column for that. You cannot drag a measure into a bar chart visual as a dimension. 

I hope that helps. 

View solution in original post

2 REPLIES 2
v-stephen-msft
Community Support
Community Support

Hi @Anonymous ,

 

Measures are displayed based on dynamic aggregation results, which take up more CPU, while calculated columns are displayed based on static results, which take up more memory.

 

Best Regards,

Stephen Tao

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Applicable88
Impactful Individual
Impactful Individual

@Anonymous,   measures are computed at runtime and calculated columns needs to be stored. That means measures does not need storage space, but the latter do. They also tend to make your calculation slower, since your model grow with the columns generated. Thats the reason when possible to use measures. They are only computed when you need them. Anyway, a good reason for the need of a calculated column might be the need for a "customize" dimension that you need for a bar chart. For example your mastercalendar doesn't consist of a weeknumber to the date, than you need to create one with weeknumber() - function. And now go further that you want to to have a bar chart dimension, where your calendar week is concatenated with the year number together á la " 2021 / 40 " . If you want a customized dimension you need a calculated column for that. You cannot drag a measure into a bar chart visual as a dimension. 

I hope that helps. 

Helpful resources

Announcements
Join Arun Ulag at MPPC23

Join Arun Ulag at MPPC23

Get a sneak peek into this year's Power Platform Conference Keynote.

PBI Sept Update Carousel

Power BI September 2023 Update

Take a look at the September 2023 Power BI update to learn more.

Learn Live

Learn Live: Event Series

Join Microsoft Reactor and learn from developers.

Dashboard in a day with date

Exclusive opportunity for Women!

Join us for a free, hands-on Microsoft workshop led by women trainers for women where you will learn how to build a Dashboard in a Day!

Top Solution Authors