Work days, index field for every granularity of time (for fiscal calendars that don&#x27;t align to calendar granularities), day number of every time span, display fields stored in text (&quot;I don&#x27;t care about the intricacies of date formatting in locales, just make it always look like this &quot;), abbreviations of display fields.<p>How about the retail requirement of capturing store open&#x2F;close status for year on year comparisons? Date dimension becomes Store_Date dimension, with indicators for what to include&#x2F;exclude in comparison totals?<p>I give trainings on dimensional modeling and query design&#x2F;optimization. The vast majority of my examples are for dates, for two reasons.<p>1. Everyone needs some form of date dimension.<p>2. If you can solve date problems, you can apply any other logic you want trivially.<p>2 is not 100% true, but sometimes it seems that way.