Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hello everyone
I'm starting in Power BI and i have this "simple" question
If i need to create a Data Table in Power BI, whats is the best aproach?
Use Dax ou User PowerQuery/M
I've created 2 PBIX files, one for DAX and another to M, they are almost equal using Vertipaq in DAX Studio.
Can anyone diferences in performance or storage? and best aproach in real world projects.
Thanks in advance.
Fausto Caveiro
Solved! Go to Solution.
I recommend M/Power Query. It is recognized as imported data by DAX and has good compression. It can be fully dynamic as well, adding years as your data increases over time, and removing earlier years if you don't want to keep history forever. For example, last 5 years or whatever. See my blog on how to do this.
Creating a Dynamic Date Table in Power Query
If you use DAX, I recommened a calculated table, not a table with calculated columns. The latter will not perform as well.
In general, try to avoid calculated columns. There are times to use them, but it is rare. Getting data out of the source system, creating columns in Power Query, or DAX Measures are usually preferred to calculated columns. See these references:
Calculated Columns vs Measures in DAX
Calculated Columns and Measures in DAX
Storage differences between calculated columns and calculated tables
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingI recommend M/Power Query. It is recognized as imported data by DAX and has good compression. It can be fully dynamic as well, adding years as your data increases over time, and removing earlier years if you don't want to keep history forever. For example, last 5 years or whatever. See my blog on how to do this.
Creating a Dynamic Date Table in Power Query
If you use DAX, I recommened a calculated table, not a table with calculated columns. The latter will not perform as well.
In general, try to avoid calculated columns. There are times to use them, but it is rare. Getting data out of the source system, creating columns in Power Query, or DAX Measures are usually preferred to calculated columns. See these references:
Calculated Columns vs Measures in DAX
Calculated Columns and Measures in DAX
Storage differences between calculated columns and calculated tables
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi Edhans
Many many thanks for you fast answer!
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 6 | |
| 5 | |
| 4 |
| User | Count |
|---|---|
| 26 | |
| 17 | |
| 13 | |
| 10 | |
| 9 |