Forum Discussion
Would Enabling Large Semantic Model Storage Format Improve Refresh Performance?
- 1 month ago
Hi manoj_0911 ,
Yes, you can enable it as its recommended by Msft and the semantic model can grow beyond the size during refresh and it handles the XMLA operarion in a better way . While it will not reduce the load on your SQL server, it provides significant backend benefits for your Fabric/Premium capacity:
- SQL Server Load: Zero impact. It does not change how data is queried or extracted from the source.
- Refresh Efficiency: Much faster and safer "commit" phase. It writes to disk incrementally during the refresh, significantly reducing memory spikes and Out-Of-Memory failures.
- Capacity Health: Datasets load back into memory faster for end-users, improving overall Premium capacity performance.
- The Only Downside: Once enabled, you cannot download the dataset back to a local `.pbix` file. (Always maintain the latest copy of the PBIX in sharepoint or a common drive)- Bottom line: Enable it to future-proof your dataset's reliability and protect your capacity's memory as your 3-year archive grows.
https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/service-premium-large-models?source=docsThanks!
Natarajan Manivasagan
If you found this helpful, please consider giving it a Kudos and marking it as the accepted solution โ it goes a long way in helping others facing the same issue.๐ Best Solution for Enterprise BI โ 2026 Microsoft Fabric Semantic Link Developer Experience Challenge
๐ Microsoft announcement ยท View the winning notebookFor more Power BI tips and discussions, let's connect on LinkedIn.
Cheers!
Hi manoj_0911 ,
Yes, you can enable it as its recommended by Msft and the semantic model can grow beyond the size during refresh and it handles the XMLA operarion in a better way . While it will not reduce the load on your SQL server, it provides significant backend benefits for your Fabric/Premium capacity:
- SQL Server Load: Zero impact. It does not change how data is queried or extracted from the source.
- Refresh Efficiency: Much faster and safer "commit" phase. It writes to disk incrementally during the refresh, significantly reducing memory spikes and Out-Of-Memory failures.
- Capacity Health: Datasets load back into memory faster for end-users, improving overall Premium capacity performance.
- The Only Downside: Once enabled, you cannot download the dataset back to a local `.pbix` file. (Always maintain the latest copy of the PBIX in sharepoint or a common drive)
- Bottom line: Enable it to future-proof your dataset's reliability and protect your capacity's memory as your 3-year archive grows.
https://learn.microsoft.com/en-us/fabric/enterprise/powerbi/service-premium-large-models?source=docs
Thanks!
Natarajan Manivasagan
If you found this helpful, please consider giving it a Kudos and marking it as the accepted solution โ it goes a long way in helping others facing the same issue.
๐ Best Solution for Enterprise BI โ 2026 Microsoft Fabric Semantic Link Developer Experience Challenge
๐ Microsoft announcement ยท View the winning notebook
For more Power BI tips and discussions, let's connect on LinkedIn.
Cheers!