bridge table issues with dimensional model
2 posters
Page 1 of 1
bridge table issues with dimensional model
suppose we have 1 dimension table: RULES
1 fact table: AUDIT
each audit trail may use multiple rules. each rules may be used by multiple audits.
in this case, we may utilize a bridge table to handle M:M relationship.
but if we do so, the RULES dimension won't be like an dimension.
it has to be changed frequently, as frequent as AUDIT table.
does anybody have better solutions for this situation?
1 fact table: AUDIT
each audit trail may use multiple rules. each rules may be used by multiple audits.
in this case, we may utilize a bridge table to handle M:M relationship.
but if we do so, the RULES dimension won't be like an dimension.
it has to be changed frequently, as frequent as AUDIT table.
does anybody have better solutions for this situation?
aug828- Posts : 5
Join date : 2012-06-13
Re: bridge table issues with dimensional model
Step back and think about what it is you are trying to accomplish.
What process are you trying to represent?
What are the actions/events/states that occur during the process?
What is the context for these actions/events/states?
What process are you trying to represent?
What are the actions/events/states that occur during the process?
What is the context for these actions/events/states?
Similar topics
» How to Model Single-Table Parent-Child Relational Table in a Dimensional Schema
» How do you properly model with a bridge table
» General Ledger Fact Table: Dimensional Model
» Dimensional Model: Connecting dimension to fact table using two approaches
» Single fact table vs multiple fact tables - what is the right way in a dimensional model?
» How do you properly model with a bridge table
» General Ledger Fact Table: Dimensional Model
» Dimensional Model: Connecting dimension to fact table using two approaches
» Single fact table vs multiple fact tables - what is the right way in a dimensional model?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum