Forum Discussion
Relationship with Fact tables
- 1 month ago
Hi,
In a dimensional model, it is generally recommended **not to create a direct relationship between two fact tables**. Instead, both fact tables should share common dimension tables (such as Date, Customer, Product, or Location) in a star schema. This approach keeps the model simpler, avoids ambiguous filter paths, and usually provides better performance.
If the two fact tables need to be analyzed together but don't share the same grain, consider using shared dimensions or, where appropriate, a bridge table instead of creating a direct fact-to-fact relationship.
Could you share:
* The structure of your two fact tables.
* The columns you are trying to relate.
* The business scenario you're trying to achieve.That will help the community recommend the most appropriate modeling approach.
Hi thank you for all your suggestions. One of the tables mustn't have had unique values in the primary key field that's why I wasn't able to create a relationship for. However, I did a workaround with the Dimension table Kiran-7312 which helped remove all duplicates. I also just split the data out into two reports as it looked better that way anyway aesthetically. Thank you all for your help with this.