Forum Discussion
Gandalf12345
Advocate I
Advocate IModelling Advice: Fact or Dimension Table
Hello everyone, Can you please give me a short input on what would be the best start to model the following screnario: We have the following tables 1. "ticket": this holds information on the produ...
Gandalf12345Advocate I
Advocate IIf I understand that correctly, I would then have sth like the following
| Ticket ID | machine id | location id | manager id | creation date | offer ID | Offer Price | Time Entry ID | Time Entry Person | Duration (min) |
| 1 | M1 | L1 | E1 | 01/01/24 | O1 | 100 | T1 | A1 | 60 |
| 1 | M1 | L1 | E1 | 01/01/24 | O1 | 100 | T2 | A1 | 30 |
| 1 | M1 | L1 | E1 | 01/01/24 | O2 | 50 | T1 | A1 | 60 |
| 1 | M1 | L1 | E1 | 01/01/24 | O2 | 50 | T2 | A1 | 30 |
Would not this create a really, really huge table then? Or did I misunderstand?
Wilson_
Memorable Member
Memorable MemberLooks like we're on the same page. What do you mean by a "really, really huge table"?
- Gandalf12345
Hi Wilson_
we have ~10 million tickets, 20 million time entries and 13 million offers. If I have them in 1 table I would combine basically every time entry with every offer, wouldn't I? That would make the combined table enormous.As an example: 1 ticket, 2 offers, 2 times entries would result in the table in the previous post (4 lines with the offers and time entries twice)
Having 3 offers and 3 time entries on that ticket would lead to 9 rows.
Am I missing something here?
Best regards
Gandalf