Is "Month" leve mandatory for a Time Dimension?
4 posters
Page 1 of 1
Is "Month" leve mandatory for a Time Dimension?
One of my colleagues suggested to have only "Year" and "Day" level for a Time Dimension to improve the cube performance for one of our projects. His idea is that if the customer wants a Month level, he/she can query from the underlying data mart directly. I don't agree with it. Please advise whether a "Month" level could be omitted in a Time Dimension.
sapisfun- Posts : 1
Join date : 2013-02-06
Re: Is "Month" leve mandatory for a Time Dimension?
You could drop anything you want. Question is, does it make sense?
Re: Is "Month" leve mandatory for a Time Dimension?
How does that improve performance? There are just as many rows in the dimension.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: Is "Month" leve mandatory for a Time Dimension?
It is unlikely to make any difference to performance and having to go to two different places (cube and mart) for similar queries doesn't make sense (or a great user experience)
thedude- Posts : 21
Join date : 2009-02-03
Location : London
Similar topics
» Using the Date Dimension for Summary Fact Tables or new specialized Month Dimension?
» Time of Day Dimension
» 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
» when to use a seperate month dimension?
» Time of Day Dimension
» 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
» when to use a seperate month dimension?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum