Hi all,

Looking for some suggestions to implement time and calendar data within a
DWH.

I've done a fair bit of investigating best practices for implementing time
as a dimension within a DWH, but none of them talk about breaking time down
by calendar types and i'm wondering if there is a reason for it.

I mean, of course we can easily implemtn the standard calendar into a time
dimension, but when it comes to hosting more than 1, i.e. Fiscal, Financial
and other Calendars that business may use, isn't there a need here to hold
daily information broken down into different calendars? I mean, there will
be different start and end dates, different groupings within these, i.e.
Qtrs, Months and Weeks that may start and end on different dates to the
normal calendar.

So my question is, is the best way to implement TIME as a dimension by
having an ID and then many attributes about this date, which means having
many columns to perform different calculations OR is it best to introduce a
calendar type system, for example, StandardCalendar, FiscalCalendar,
FinanicalCalendar etc... where each holds its own information that can be
joined back to a TimeID+CalendarID?

I have a sneaky suspicion i've just rambled on and made no sense to anyone ?

Many thanks
Immy