Home
Kimball Group Home
Search
Register
Log inFact joins twice dimension
Page 1 of 1
Fact joins twice dimension
ric79 Wed Nov 21, 2012 3:41 pm
Hi all,
I need to model this case:
1) RELATIONSHIPS between NODE_ORIGIN and NODE_DESTINATION
2) Collect daily statistics for RELATIONSHIPS
Both NODE_ORIGIN and NODE_DESTINATION are described in a single dimension called NODE.
I create a dimension called RELATIONSHIP as factless fact linking twice the NODE.
I create a fact pointing DATE and RELATIONSHIP dimensions.
Is it better to create a fact pointing direcly to NODE_ORIGIN, NODE_DESTINATION, DATE and bypass the RELATIONSHIP dimension?
Riccardo
I need to model this case:
1) RELATIONSHIPS between NODE_ORIGIN and NODE_DESTINATION
2) Collect daily statistics for RELATIONSHIPS
Both NODE_ORIGIN and NODE_DESTINATION are described in a single dimension called NODE.
I create a dimension called RELATIONSHIP as factless fact linking twice the NODE.
I create a fact pointing DATE and RELATIONSHIP dimensions.
Is it better to create a fact pointing direcly to NODE_ORIGIN, NODE_DESTINATION, DATE and bypass the RELATIONSHIP dimension?
Riccardo
ric79- Posts : 4
Join date : 2009-08-20
Similar topics» Too much of inner joins-ETL Strategy to load into Dimension
» Modeling an Employee Dimension to a Fact which has two columns relating to the Dimension
» Conformed Dimension for Transaction Fact and Accumulating Snapshot Fact Table
» Is it good to have dimension table alone instead of having both fact and dimension... in this scenario?
» Modeling an Employee Dimension to a Fact which has two columns relating to the Dimension
» Conformed Dimension for Transaction Fact and Accumulating Snapshot Fact Table
» Is it good to have dimension table alone instead of having both fact and dimension... in this scenario?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum