For a relational model the easiest solution is to have a database view on the date/time table that stores columns relating to YTD and such. You can then define different grain for YTD calculations, like having a YTD based on whole months and one for the day-level.
Extremely roughly division:
Dimensional model is great for analysis, relational (flattened) is much easier for a casual user and for pure , fixed management reports
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.