Handling peak time by location
2 posters
Page 1 of 1
Handling peak time by location
How can build the ability to report on "peak periods" into my design?
Peak periods in my application are different for each location and even different on different days. On days before a holiday, they are like Fridays, on holidays, a Saturday or Sunday, etc.
I'm considering Peak as a degenerate dimension with a Y/N assigned by ETL but can't help wondering if there is a better way.
Peak periods in my application are different for each location and even different on different days. On days before a holiday, they are like Fridays, on holidays, a Saturday or Sunday, etc.
I'm considering Peak as a degenerate dimension with a Y/N assigned by ETL but can't help wondering if there is a better way.
Re: Handling peak time by location
It depends. You could create a dimension whose natural key is location and date, but if the only attribute is the peak indicator, you are better off storing it as a degenerate dimension on the fact. If there are other attributes dependent on location and date (or expect such attributes in the future), it would be worthwhile to build a dimension table.
Similar topics
» Combined Date Time dimension vs. Separate Day and Time dimensions and timezones
» Time dimension design for cross time zone and custom calendar warehouse, 1min granularity
» Time Dimension, NULLs and Time datatype
» Location and department (n:m)
» Location in Each Dimension?
» Time dimension design for cross time zone and custom calendar warehouse, 1min granularity
» Time Dimension, NULLs and Time datatype
» Location and department (n:m)
» Location in Each Dimension?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|