Quarter/month granularity-Generic key

[#1]

‌Hi all, just wanted to get some advice on best approach to model some simple data that has some common fields (so will be building a single fact) but is at different granularity, i.e., some is Quarter level and some Month level.

Would using a link dimension with generic key be the best option, so something like

e.g.

Q1|Jan|Feb|Mar

or

Q1|Jan

Q2|Feb

Q3|Mar

Many thanks in advance!

[Gysbert_Wassenaar]

Create a calendar table instead that contains the dates, months, quarters and years. A month determines the quarter so there's no need to put both in a key.

[#3]

Hi, thanks for the reply, if my data is like in the attachment, can I just ask how you would join to the Calendar dimension, would i use a composite key of Year&Quarter as join???

Thanks!