Fact Design and best practices
2 posters
Page 1 of 1
Fact Design and best practices
This is design question.
What if designing Order Line Items Fact.. However, not every order has line items.
Would you design Order Facts and Have line items as dimension?
or
Order Line Items Facts, but then what is the best practice to represent orders without line items?
or
would you create 2 separate facts which create another set of issues?
Thanks in advance.
What if designing Order Line Items Fact.. However, not every order has line items.
Would you design Order Facts and Have line items as dimension?
or
Order Line Items Facts, but then what is the best practice to represent orders without line items?
or
would you create 2 separate facts which create another set of issues?
Thanks in advance.
sam119- Posts : 2
Join date : 2012-10-05
Re: Fact Design and best practices
What's an order without a line item? It sounds like the business in an inconsistent state.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Design
I used order as an example. It is transactions, not every transaction has line items.
Thanks.
Thanks.
sam119- Posts : 2
Join date : 2012-10-05
Re: Fact Design and best practices
OK, got it. If one of the columns that defines the grain is optional, you can't build the fact at that level. In this case you would need two facts.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Similar topics
» FACT Design Question - How to design FACT Table when computation is required on the degenerate dimension?
» Best practices for a Fact table that contains a row per date/hour/location/patient stay
» FACT Design
» Fact Table Design
» Two-Part Fact Design Question
» Best practices for a Fact table that contains a row per date/hour/location/patient stay
» FACT Design
» Fact Table Design
» Two-Part Fact Design Question
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum