Julian Date and Supplemental Month (budgeting)

During some research on time dimensions in Analysis Services, I stumbled across this interesting article by Dylan Wan (Blog|Linkedin). These are some very good design tips, indeed, but unfortunately, in my case, I had embrace the concept of a supplemental month (might be it has another term in English). A month that is added to the end of a year, in order to keep track of changes made to the year just passed. Changes like these cannot occur in the following year, where they actually occur, but must be tied to the previous year.
I cannot see any way of dealing with this kind of “feature” in a system build on a Julian Date.

Any thoughts on this?

2 thoughts on “Julian Date and Supplemental Month (budgeting)

  1. let your correction fact rows point to unknown in the date dimension, and add a new dimension called DimSupplementalBudgetingMonth. Normal fact rows points to unknown in this dimension. Correction fact rows points to this dimension


    1. But that would leave you with two time dimensions. The two would then have to be connected through an intermediate dimension, in order to let the user browse by the one, true, time dimension.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.