on 05-29-2014 4:31 PM
Why would you not set the cardinality of a join?
Set the cardinalities for joins as you create them. You cannot detect contexts without them and they add further documentation to the universe - other universe designers will understand your design more easily.
As for a default cardinality, there's no such thing. Default is to set the correct cardinality for that particular join. For joining a dimension to a fact table, default is 1 dimension to many facts.
Be clear though, the cardinalities do not directly affect the SQL generated; they only have an impact on the SQL indirectly - that is, when they are used to detect contexts. It is the contexts themselves that have an impact on SQL generated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi…
If you join two tables with Cardinality with UnKnow or one-to-one (1,1) or one-to-many (1,N) or many-to-one (N,1) or many-to-many (N,N)) will get the same results.
Cardinality plays role while considering context (one-to-one (1,1) or one-to-many (1,N)) .
So cardinality (Default, 1:1,1:N,N:1,N:N) gives the same results.
Please find the below doc for more info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.