I had a similar table in a transaction system that eventually the users wanted to measure time between events.
I create a Fact table that has Date and Time dimension tables linked to it as well as Minute Difference columns in the fact table. The ETL handled the calculations and 5-6 rows in the Registration transaction table became one row in the RegFact table.
CREATE TABLE (fact.Registration)
( RegID int, EnterQueueDateID int, EnteredQueueTimeID int, MarkAtDeskDateID int, MarkAtDeskTimeID int, EnteredQueueMarkAtDeskMinutes int...)
)
Instead of a factless fact, we had minute difs in the table. If i had other columns for the fact table, they became dimensions like Office, Recruiter, etc.
Thomas
TheSmilingDBA Thomas LeBlanc MCITP 2008 DBA
.
social.technet.microsoft.com/Forums