Forum Discussion
Semantic model Refresh memory limit error
- 7 months ago
Hii HaidersBSKY
This usually isn’t about the final VertiPaq size, but the peak memory needed during refresh. During refresh, Power BI temporarily holds multiple copies of tables, expands dictionaries, builds relationships, and runs partitions in parallel, which can push memory far beyond the stored model size. Models with high-cardinality columns, large text fields, many calculated columns, or complex relationships can spike memory even if the VertiPaq footprint looks small. To fix this, reduce refresh parallelism, remove unnecessary columns (especially text/IDs), lower cardinality where possible, avoid calculated columns, and consider incremental refresh. Also ensure the capacity has enough headroom at refresh time, as other workloads can cause refreshes to fail despite smaller models.
Hii HaidersBSKY
This usually isn’t about the final VertiPaq size, but the peak memory needed during refresh. During refresh, Power BI temporarily holds multiple copies of tables, expands dictionaries, builds relationships, and runs partitions in parallel, which can push memory far beyond the stored model size. Models with high-cardinality columns, large text fields, many calculated columns, or complex relationships can spike memory even if the VertiPaq footprint looks small. To fix this, reduce refresh parallelism, remove unnecessary columns (especially text/IDs), lower cardinality where possible, avoid calculated columns, and consider incremental refresh. Also ensure the capacity has enough headroom at refresh time, as other workloads can cause refreshes to fail despite smaller models.
Alright thanks, will try removing unnecessary columns and reducing refresh parllelism further.