whats best? Big flat fact table or smaller fact table with one dimension?

[EricMamet]

Hello there, I am "relatively" new to PowerBI (~Vertipaq)

We have a relatively simple datamart design with one fact table (fairly "fat" already) and a "generic" dimension where the properties are actually value/pairs in a JSON column (called PDS_MODEL_FEATURES in the diagram below).

We know the list of value/pairs present in the JSON column (held as metadata in other tables).

From a PowerBI perspective, would it be better to project the value/pairs onto the fact table, making it a single "fatter" fact table.

Or would it be better to keep a separate dimension (we would expose the value pairs as Pseudo columns)?

[amitchandak · Accepted solution]

@EricMamet , for power bi star schema is better.

refer

https://radacad.com/power-bi-basics-of-modeling-star-schema-and-how-to-build-it

https://docs.microsoft.com/en-us/power-bi/guidance/

https://docs.microsoft.com/en-us/power-bi/guidance/star-schema

refer

Best Practices
https://maqsoftware.com/expertise/powerbi/power-bi-best-practices
https://docs.microsoft.com/en-us/power-bi/guidance/power-bi-optimization
https://www.c-sharpcorner.com/article/power-bi-best-practices-part-1/