Forum Discussion
Star Schema: Multiple Dates
Nothing wrong with having multiple date tables. Particularly if you want to use more than one of then at a time, or don't want to over complicate measures. They tend to be quite small.
The advantage of a single date table is when you want to have measures that involve different date but have to be on the same access. For example order and sales dates. You want the count of sales to be on the date they sales occur and orders on the the day those occured. A common date table would be required in that case, with measures that involve userelationship() to activate a relationship
Nothing wrong with having multiple date tables. Particularly if you want to use more than one of then at a time, or don't want to over complicate measures. They tend to be quite small.
The advantage of a single date table is when you want to have measures that involve different date but have to be on the same access. For example order and sales dates. You want the count of sales to be on the date they sales occur and orders on the the day those occured. A common date table would be required in that case, with measures that involve userelationship() to activate a relationship