Forum Discussion
Post ProdigyModelling a large customer table in Fabric
Hi pmscorca
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks
Post ProdigyHi, I think that is enough to reply by leveraging on some key concepts.
Having a customer registry with core/header data and some other data with a 1-to-m relationship should represent a pattern scenario, manageable thinking to a dwh by a dimensional model based on a star schema, but thinking to a big data modeling?
Fabric allows to create lakehouses and warehouses, based on Spark delta tables: this format is more performant and has a columnar data organitazion, perfectly suitable to big data.
Moreover, Fabric allows to partition table f.e. respect to a date and so a dimension could be handle in a different manner than a SCD one.
Does the columnar organization of the delta tables for a big data scenario suffer to have more null values?
Fabric allows to implement a big data solution, by his features, but to handle big data occurs to go beyond the known data modeling approaches (E/R model, dimensional model and so on).
In these terms, is it possible to have an initial reply for my issue? Thanks