You are designing a data warehouse with two fact tables. The first table contains sales per
month and the second table contains orders per day.
Referential integrity must be enforced declaratively.
You need to design a solution that can join a single time dimension to both fact tables.
What should you do?
A.
Create a time mapping table.
B.
Change the level of granularity in both fact tables to be the same.
C.
Merge the fact tables.
D.
Create a view on the sales table.
A
0
1
According to this
http://ms-olap.blogspot.com/2010/01/different-granularity-in-single.html
A seems right
0
0
via the link you gave it confirms that B is the correct answer he was Changing the level of granularity from month to day.
0
0
its A
0
0
A is correct
0
0
I agree with dennis
0
0
What you all mean by “Create a time mapping table”?
I think the right answer is B.
I have to convert the fact month column to date format (1st or Last day of
each month) and join the tables on day granularity.
If you join the month granularity fact table with
date dimention (on month and year) every fact row multiplied by
by number of days in the month.
The ssas solution works because it eliminates such effect.
1
0
“You need to design a solution that can join a single time dimension to both fact tables.”
Question doesnt says “how to make a query with this scenario”.
Then, if you need to design a solution, you must create a single time dimension and map this table.
A is correct.
0
0
“B” is correct even based on your post: There is already a time dimension and the question is how to design a solution in both tables.
0
0
A is Right.
0
0
OK… But you have another question, strictly identical, and the choice “Mapping Table” is not presented…
If we refer to that, the answer would be “Change level of granularity”
0
0
A
0
0
answer should be B
0
0
You are designing a data warehouse with two fact tables. The first table contains sales per month and the second table contains orders per day. Referential integrity must be enforced declaratively. You need to design a solution that can join a single time dimension to both fact tables. What should you do?
Join the two fact tables.
Merge the fact tables.
Create a time dimension that can join to both fact tables at their respective granularity.
Create a surrogate key for the time dimension.
0
0
Create a time dimension that can join to both fact tables at their respective granularity.
0
0
thnq sir
0
0
You are designing a data warehouse with two fact tables. The first table contains sales per month
and the second table contains orders per day. Referential integrity must be enforced declaratively.
You need to design a solution that can join a single time dimension to both fact tables. What should
you do?
A. Create a view on the sales table.
B. Partition the fact tables by day.
C. Create a surrogate key for the time dimension.
D. Change the level of granularity in both fact tables to be the same.
0
0
Not an expert, but I am saying D for this one.
0
0
Can anyone explain what a time-mapping table is?
0
0
I think B is correct answer.
0
0