Is it a fact or a dimension?
3 posters
Page 1 of 1
Is it a fact or a dimension?
The fact is an atomic financial transaction. Each transaction results in 0 to n contributions, each a certain percentage of the transaction.
In the source database, these are related tables, call them Transaction and Contribution, where Contribution has a foreign key to Transaction.
The question is this: Should Contribution be a Fact or a Dimension? If it is a fact, how should I join them?
In the source database, these are related tables, call them Transaction and Contribution, where Contribution has a foreign key to Transaction.
The question is this: Should Contribution be a Fact or a Dimension? If it is a fact, how should I join them?
Re: Is it a fact or a dimension?
Not enough details, but based on the information, contribution sounds like a dimension
modeling12345- Posts : 2
Join date : 2014-01-30
Re: Is it a fact or a dimension?
It sounds like both are facts. The contribution fact would contain transaction ID as a degenerate dimension, so would the transaction fact. It would probably also have many of the same dimensions as the transaction facts plus those related to the contribution. There would not be a foreign key from contribution to transaction.
Similar topics
» Dimension Design with intermediate tables between fact and dimension
» Using the Date Dimension for Summary Fact Tables or new specialized Month 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
» Using the Date Dimension for Summary Fact Tables or new specialized Month 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
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|