Forum Discussion
Calculated Table causes performance issue and dataset refresh fails
- 2 years ago
When you create a calculated table, the entire uncompressed table must be materialized in memory and then compressed. This could be a memory-intensive operation that works on your PC and fails on Power BI Service.
You should reduce that table by removing unused columns and remove unnecessary rows - e.g. keep only the rows that have an issue.
Or compute the column outside of Power BI, so it's processed like other tables segment by segment, reducing the memory requirement at refresh time.
When you create a calculated table, the entire uncompressed table must be materialized in memory and then compressed. This could be a memory-intensive operation that works on your PC and fails on Power BI Service.
You should reduce that table by removing unused columns and remove unnecessary rows - e.g. keep only the rows that have an issue.
Or compute the column outside of Power BI, so it's processed like other tables segment by segment, reducing the memory requirement at refresh time.