March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi all,
Just asking some advice here:
For a new to-be-designed data warehouse: Would you go with an integer date key or a Date date key for referencing the Date dimension?
If I understand it well, both are possible. I just need to mark the date dimension as a date table and have a Date column marked as such. However, I did a test with an integer column but the TotalYTD dax function doesn't seem to work with that.
Any advice?
Thanks
Solved! Go to Solution.
Hi @ntimmerman
@AnalyticPulse Thank you very much for your prompt reply. Allow me to add something here.
Using an integer date key is a traditional approach where dates are represented in a format. This method is beneficial for performance reasons, as joining on integers is generally faster than dates.
However, it can make date calculations more complex, as you’ve noticed with the function not working properly with integer keys.
On the other hand, a Date data type key is more intuitive and aligns with the natural representation of dates.
Given your experience with the function not working with an integer column, it seems that using a Date data type might be more suitable for your needs.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @ntimmerman
@AnalyticPulse Thank you very much for your prompt reply. Allow me to add something here.
Using an integer date key is a traditional approach where dates are represented in a format. This method is beneficial for performance reasons, as joining on integers is generally faster than dates.
However, it can make date calculations more complex, as you’ve noticed with the function not working properly with integer keys.
On the other hand, a Date data type key is more intuitive and aligns with the natural representation of dates.
Given your experience with the function not working with an integer column, it seems that using a Date data type might be more suitable for your needs.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you @v-nuoc-msft and @AnalyticPulse ! I will do some more experimenting but will probably change to using a date field as date key. Thanks again
if you use the Date format will simplify your date dimension because it is easiert work with date datatype when you want to debug something in your file. if the data source use the integer date key you can consider to cintinue with same for uniformity so you can avoid transformation complexity. integer keys are also space efficient .
https://analyticpulse.blogspot.com/2024/04/case-study-banking-and-finance.html
My blog:
https://analyticpulse.blogspot.com/
https://analyticpulse.blogspot.com/2024/04/case-study-powerbi-dashboard-developer.html
See my Pins :
https://pin.it/5aoqgZUft
https://in.pinterest.com/AnalyticPulse/
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
32 | |
24 | |
12 | |
11 | |
9 |
User | Count |
---|---|
47 | |
46 | |
23 | |
12 | |
9 |