One semantic model is better/worse than N semantic models?

[rbrandsbi]

Hey guys,

I have a client who has like 15 reports - comercial, HR, Delivery, etc...

All 15 reports have the same semantic model. This semantic model has all tables, relationships and measures.

So, what is the best way - 1 semantic model per report ou 1 semantic model to all the reports I have?

[v-yilong-msft]

Hi @rbrandsbi ,

As tazzbh said, all reports use a semantic model. It keeps things neat and tidy. Here are my thoughts and additions on the subject.

Using one semantic model for all reports maintains consistency, and sharing metrics and relationships ensures consistency across all reports, but if there is a problem with the shared model, it affects all reports at the same time, and a single model may not be the best long term solution if your client plans to expand significantly.

One semantic model per report allows each report to have its own semantic model to minimize the risk of affecting other reports. You can also customize each model to meet specific reporting requirements, but managing multiple models can be more complex and time-consuming, and there may be similar tables and relationships in different models.

Overall, if your client's current setup is working well and they don't anticipate major expansion, use a shared semantic model. If customization and independence are critical, consider using a separate model for each report.

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[tazzbh · Accepted solution]

Hey!

I'd say go for one semantic model for all the reports. It keeps things tidy and you won't be duplicating stuff., once change in one place affect all reports. But watch out, if something goes wrong in the shared model, it messes up all the reports at once. And if your client's planning to scale up, one model for all reports might not be the best option. Keep an eye on scalability!