Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
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.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
34 | |
21 | |
20 | |
14 | |
12 |
User | Count |
---|---|
21 | |
18 | |
18 | |
14 | |
14 |