Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
IvanR
Regular Visitor

Date-time analysys for call center agents modeling

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!

1 REPLY 1
lbendlin
Super User
Super User

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.

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors