Forum Discussion
PowerBI refresh timeout in Shared capacity
- 1 year ago
At first I tried Model optimization, Query optimization etc. Also considered incremental refresh. But all that didn't help since id doesn't load at all then incremental refresh wans't an option.
In the end the problem was multiple calculated colums on a large table. After moving them to Data import steps, it worked like a charm. It seems that PowerBI is hard to manage RAM resource limitations during those calculated column refreshes.
Hi, Asnate
The issue is likely due to Shared Capacity limitations. To resolve it:
- Optimize Model: Remove unused columns/tables and aggregate data.
- Enable Incremental Refresh: Refresh only new/changed data.
- Optimize Queries: Improve source query performance.
- Upgrade to Premium/PPU: Shared Capacity may lack resources for large models.
- Schedule Off-Peak Refreshes: Avoid refreshing during busy times.
If issues persist, consider splitting the dataset or upgrading to dedicated capacity.
Thank you for your answer. But isn't it still weird that in Premium Capacity data could refresh in 20-30 minutes and the model size is below 1GB. So shouldn't Microsoft provide that model refresh works? Or is there any other known limitations of Shared Capacity besides model size, workspace size and 2h timeout and common pool for PowerBI customers?