Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi
We have a massive data set. We enabled incremental load on one transactional table. and published to service. In service, the dataset failed due to this issue
| The database was evicted and the operation cancelled to load balance the CPU load on the node |
Solved! Go to Solution.
Individual partitions cannot exceed 10GB. A refresh request cannot exceed 5 hours. You may be hitting one or both of these limits just with this semantic model but not with the others.
Use bootstrapping for the partition definitions and then manually refresh the historical / cold partitions vial the XMLA endpoint.
Thanks for the article. I have other models also established in the same way. I dont experience this error in other incremntal load configured model. So it looks weird that this is happening only in this model alone
Individual partitions cannot exceed 10GB. A refresh request cannot exceed 5 hours. You may be hitting one or both of these limits just with this semantic model but not with the others.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 16 | |
| 14 | |
| 9 | |
| 9 | |
| 8 |
| User | Count |
|---|---|
| 33 | |
| 29 | |
| 27 | |
| 25 | |
| 25 |