Forum Discussion

ablarrosa8's avatar
ablarrosa8
Helper I
11 months ago
Solved

Differences between small data model vs. a large data model in Microsoft Fabric

Hello,   When should I choose a small data model vs. a large data model in Microsoft Fabric, and what are the key differences in terms of performance, governance, and scalability?   Thanks in adv...
  • AntoineW's avatar
    11 months ago

    Hello ablarrosa8,

     

    Size limits and scalability

    • Small data models

      • By default, semantic models (datasets) are limited to 1 GB when hosted in shared capacity or with Pro/PPU without Premium/Fabric capacity.

    • Large data models

      • By enabling the Large semantic model storage format, models can exceed 1 GB.

      • The maximum size is then defined by your Fabric or Premium capacity SKU (F-SKU, P-SKU, Embedded A SKU) or by the capacity admin.

     

    Activation and setup

    • The Large model storage format is enabled in the dataset settings in the Power BI/Fabric service.

    • For existing models, no republishing from Power BI Desktop is required—just turn the setting On in the service.

     

    Performance trade-offs

    • Small models → faster refresh, queries, and lower resource consumption.

    • Large models → scalable, enterprise-grade, but more resource-intensive and dependent on capacity.

     

    Additional benefits

    • XMLA write performance: Even if your model is small, enabling the large format improves XMLA write operations.

    • Default partitions: Large models use 8M-row default partitions, consistent with Azure Analysis Services best practices.

     

    Source : https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/service-premium-large-models

     

    In general, stick with a small model for simplicity, performance, and lower resource usage.
    But if your dataset grows in volume or you need better performance at scale, activate the large semantic model format to leverage enterprise-grade features.

     

    Hope it can help you!

    Best regards,

    Antoine