Forum Discussion
Modelling Advice: Fact or Dimension Table
Gandalf12345,
Since 1, 2 and 3 are all ticket level facts, you might consider joining them all into one fact table.
----------------------------------
If this post helps, please consider accepting it as the solution to help other members find it quickly. Also, don't forget to hit that thumbs up and subscribe! (Oh, uh, wrong platform?)
P.S. Need a more in-depth consultation for your Power BI data modeling or DAX issues? Feel free to hire me on Upwork or DM me directly on here! I would love to clear up your Power BI headaches.
If 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?
Looks like we're on the same page. What do you mean by a "really, really huge table"?
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