You need to design a data warehouse schema to support a multidimensional cube. The fact
table will contain multiple columns representing order dates, shipping dates, and billing
dates. The cube will contain a measure group based on the fact table.
What is the best design to achieve the goal? More than one answer choice may achieve the
goal. Select the BEST answer.
A.
In the database, create a time table for each date column in the fact table.
From the data source view, join each date column in the fact table to the corresponding time
table.
Create dimensions for each time table.
B.
In the database, create a time table containing a column that corresponds to each date
column in the fact table.
From the data source view, join each date column in the fact table to the corresponding
column in the time table.
Create a dimension for the time table.
C.
In the database, create a time table that uses an integer primary key and a datetime
column.
Create a dimension based on the time table.
From the Cube Designer, use the Dimension Usage tab to define a relationship between the
measure group date columns and the datetime column of the time dimension.
D.
In the database, create a time table that uses an integer primary key and a datetime
column.
Create a dimension based on the time table.
From the Cube Designer, use the Dimension Usage tab to define a relationship between the
measure group date columns and the key column of the time dimension.
“The fact table will contain multiple columns representing order dates, shipping dates, and billing dates.”
Doesn’t tell us the datatype. If the date is stored as an integer (i.e. 20160926) answer D. If it’s date answer C. Maybe they want to hear that you join to a date and a time table. As usual you can’t answer this question, because it doesn’t contain the necessary information. I guess it’s D, because you usually join over an integer.
0
0
I think should be B. Typical situation to employ role-playing dimension.
0
0