Forum Discussion
How to create a calendar table with second granularity?
In the Transaction table does the column you're creating the relationship on have timestamps as well? If not then you won't get any matches because the Dates aren't lining up to the Timestamps.
Generally speaking in data modeling we keep our Dates and Times separate. First, it cuts down on data volumes (only 86400 rows in the Time table and 365/366 rows per year in the Date table).
I would try that - separate your Date and Time dimension tables and separate your Dates and Times in the transaction table. Still gives you the capability to drill-down to the second level without super-sizing your model.
In the Transaction table does the column you're creating the relationship on have timestamps as well? If not then you won't get any matches because the Dates aren't lining up to the Timestamps.
Generally speaking in data modeling we keep our Dates and Times separate. First, it cuts down on data volumes (only 86400 rows in the Time table and 365/366 rows per year in the Date table).
I would try that - separate your Date and Time dimension tables and separate your Dates and Times in the transaction table. Still gives you the capability to drill-down to the second level without super-sizing your model.