Forum Discussion
Single-column dimension table
Hi hm13
You just need only two tables: one calendar table (to manage correctly dates) and your fact table will be this one ( Date, Time, Name, Process, Shift, Location, and Description).
Now you relate Date column with Calendar table (date). The relationship should be 1 to * (* this in the part of the Table with your data). Your model should be something close to this:
And now, in the slicers you just need to put the column needed.
Hi hm13
You just need only two tables: one calendar table (to manage correctly dates) and your fact table will be this one ( Date, Time, Name, Process, Shift, Location, and Description).
Now you relate Date column with Calendar table (date). The relationship should be 1 to * (* this in the part of the Table with your data). Your model should be something close to this:
And now, in the slicers you just need to put the column needed.
What would be the difference if the calendar table is created separately like you mentioned vs. just using the date column and making a date hierarchy for this column?
When you only have one table, it won't make any difficulty. However, if you add more tables (which probably includes another column of type date), you will face problem to link every database. Therefore, a Calendar Table will overcome this problem
