Forum Discussion
Data Model: Multiple Lookup Tables connected through Bridge Table
Hi, kalkhudary
Your data model design sounds very well organized, especially by bridging the IDs of the individual lookup tables through a bridge table, which ensures bi-directional communication and consistency of the data.
Here's a brief overview of the semantic model size limitations:
- For Power BI Pro, the semantic models are capped at 1 GB.
- For Power BI Premium P1, the limit is 10 GB per model.
- For Power BI Premium F32, the limit is 10 GB per model.
- For Power BI Premium F64, the limit is 25 GB per model.
In addition, the maximum size of the semantic model can be up to 100 GB when using a Power BI Premium Per User (PPU) license.
These limits are for each individual semantic model, not the sum of all models. Therefore, if you have multiple models, the size limit for each model is independent.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
kalkhudary , Ideally server should be you Fact. I am not sure how it connected with the application.
Service and sub-service should combine and give on dimension and join with the server.
Calender should join with server
amitchandak The Applications are the major fact table in this scenario since it acts as a dependency to servers and subservices.
I can combine service and subservice together and connect them to Applications however I was worried that it won't work properly with the bi-directional requirement. That is why I thought a bridging table will lessen the risk and make the bi-directional relationship more optimum.
This data model is the trickest and most challenging as the main requirement falls into reading data back and forth.
What do you think?
