If you can live with it, I would recommend the following table structure:
LOAD * Inline [
Where ... represents data I unfortunately don't have time to type in. So, "Status" is a new field which tells you which table the data originates from.
Then you can have Month as your Dimension, and your straight table expressions would be
Hopefully that made sense
thank you for the help, but i am not able to load the data in this way.
I have an operational database (no aggregates available) with one big table that has:
ID .... DateEntered DateSent DateReceived ...
I created, based on this, a start schema with the ID as a fact (and other columns) and with KeyDates for each date dimensions. See attached screenshot. I want to be able to move from a month level to a quarter or year, etc. so i need those tables as they are now.
The only way i can think of is creating a separateisland, but i'm not sure how to do that in my case, because i think i need a separate calendar table that can join with duplicates of the three time dimensions. Or not?!!?