I know that we have some hard-n-fast rules to resolve loops universe from a data warehousing system, such as : use aliases, when using the same table over and over again, but for different purposes and use contexts for each fact table.
But are there any thumb rules for resolving loops against an OLTP system?
Any insights into this would be greatly helpful to me.
The rules don’t change. Use contexts for paths and aliases for purposes. Cardinality settings on joins often indicate which situation you’re looking at.
I read, Dave… It talks about the cardinalities and how they help us detect the Chasm and Fan traps. But how do they help in fixing the loops?
Please let me know if i’m missing anything here ofcourse i’m :))