Forum Discussion
Helper IDirectLake Semantic Model failes to load due to supposed Disk Size Limit
I've "solved" it now. Scaling the Capacity of that workspace up to F64 temporarily allowed me to access the data model again, and I've removed a few of the tables that were large but not very important. Afterwards it worked on F16 again.
That being said, I still don't really understand, what exactly the problem was. To your points:
- There was no Service Issue
- I have attempted a regular refresh, though that failed. How can I manually clear a model's cache? There is no option for that in the settings.
- The problem was independent of any report, and there is no transformation in a DirectLake Model, so there were no queries to be deactivated.
- How do I check the connection? Both model and Lakehouse were in the same Fabric Workspace. I can't really affect anything there.
Super UserHi rvp_ordix , I think it is like a resource issue rather than exceeding size limits Please do try out these steps
- Check for Service Issues: Look for any ongoing issues on Power BI or Azure status pages.
- Clear Cache/Force Refresh: Try clearing the cache or refreshing the model to resolve metadata issues.
- Reduce Query Load: Temporarily disable heavy queries to ease the load.
- Check Connections: Ensure the connection between the DirectLake model and lakehouse is stable.
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
Helper II've "solved" it now. Scaling the Capacity of that workspace up to F64 temporarily allowed me to access the data model again, and I've removed a few of the tables that were large but not very important. Afterwards it worked on F16 again.
That being said, I still don't really understand, what exactly the problem was. To your points:
- There was no Service Issue
- I have attempted a regular refresh, though that failed. How can I manually clear a model's cache? There is no option for that in the settings.
- The problem was independent of any report, and there is no transformation in a DirectLake Model, so there were no queries to be deactivated.
- How do I check the connection? Both model and Lakehouse were in the same Fabric Workspace. I can't really affect anything there.