Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hello!
Help me please to decide which approach is better for model performance and an easy way to analyze data for the contact center.
Separate date time column and create date integer key and time integer key in fact table , after that connect these keys to separate dimDate and dimTime tables? Won't this approach complicate analyses (slow and complicated measures)?
or leave one DateTime column fact table as is?
Working hours, login time, etc. have to be calculated for each person and aggregated.
Thank you in advance for you answers and explanations!
The literature says to use separate date and time calendar tables to reduce the cardinality. Even with the added measure logic overhead that is still significantly faster than if you had to deal with a datetime calendar table.
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 |
|---|---|
| 97 | |
| 73 | |
| 50 | |
| 46 | |
| 44 |