Fact with more than one relation to the same dimension in the same role
2 posters
Page 1 of 1
Fact with more than one relation to the same dimension in the same role
I'm having trouble getting my wits around this. I have a Market dimension and a particular fact, the way the OLTP source is designed, can be in more than one Market, say US and AL. But it is not necessarily a hierarchy. I wouldn't want to use roles and have a Market1Key and Market2Key and I don't think I want a US/AL market key. Is there a standard solution for something like this?
Re: Fact with more than one relation to the same dimension in the same role
A bridge table is the standard solution if the number of references is not known or have no 'status' (for lack of a better word).
The 1, 2 thing doesn't work well even if there are a fixed number of references as they are difficult to use together. It only works if there is a clear precedence, an use of multiple references is not common.
The 1, 2 thing doesn't work well even if there are a fixed number of references as they are difficult to use together. It only works if there is a clear precedence, an use of multiple references is not common.
![-](https://2img.net/i/empty.gif)
» Factless Fact table or 1:M Dimension Relation
» Accumulating Fact Table Dates as Role Play Dimension and Descriptions
» Dimension relation Many-many and regular relation
» How do I join a role playing date dimension view with a Fact table in SQL Server?
» Multivalued Dimension - Employee Role
» Accumulating Fact Table Dates as Role Play Dimension and Descriptions
» Dimension relation Many-many and regular relation
» How do I join a role playing date dimension view with a Fact table in SQL Server?
» Multivalued Dimension - Employee Role
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|