Creating a separate table for storing dax measures

[mp390988]

Hi,

I created a separate table to hold my dax measures.

I noticed when I refresh my model, the "Measures (2)" table also gets included in the refresh.

My model is tiny so it does not matter but I am just thinking for big data models, is it best to exlcude this table from the refresh? I can do this by going into power query editor and tick off "Include in report refresh".

What is the best practice?

Thanks

[danextian]

Does the table contain any other data? How many rows and columns are there? If it's a very small table — say, just one row and one column — excluding it from the refresh won’t offer any noticeable performance benefits. If you intend to mark it as a measure table, make sure to assign at least one measure and then remove all  columns.

[mp390988]

No this table does not contain any other data.

It's just a table I created to contain a measure defined as below:

Count of Employee = COUNT(AttendanceData[Employee])

[v-kathullac · Accepted solution]

Hi @mp390988 ,

Thank you for reaching out to Microsoft Fabric Community Forum.

Here are few best Practices for Measure Tables :

1) Since your "Measures (2)" table only contains measures and no actual data from external sources or transformations, it doesn’t need to be refreshed.
2) It improves refresh efficiency, especially in large models.
3) A common approach is to create a blank calculated table like:
Measures = SELECTCOLUMNS({1}, "Placeholder", 1) it's not linked to a query and doesn't need a refresh
4) Use this table to store all your DAX measures for better organization.
5) No data dependency = no need to refresh during model update.

Regards,

Chaithanya.

[mp390988]

Hi @v-kathullac ,

thank you for your answer. Yes, I agree with all the points you have mentioned. I did create a separate table for just holding my measures but I did this manually by clicking "Enter Data" option under the modelling tab. 

[lbendlin]

It's an artificial construct. This "home table"  property of a measure has no technical meaning. It is purely cosmetics.

Best practice is to not have a need for a "measures table".

[mp390988]

I totally disagree with you here. All learning materials on best practices of Power Bi advise to create a separate table for holding measures.