Forum Discussion
PBI_2K26
Advocate I
1 day agoMemory issue
Hello community I get this error on a table visual in the Power BI Service in a Table visual : The context is the following Table Source : ~600M rows, Import mode, loaded from Snowflake. Ca...
ShafiUllah-bc
Resolver I
23 hours agoHi PBI_2K26 ,
One correction on the SKU point: the next size up won't help. Per the Microsoft Learn semantic model SKU limits, max memory per query is 10 GB on F64, F128 and F256. The first SKU with more is F512 (20 GB). So for this visual the query has to get smaller, not the capacity bigger.
To find what is actually using the memory:
- In Power BI Desktop, open Performance analyzer, refresh the table visual and select Copy query.
- Run that query in DAX Studio against the workspace XMLA endpoint (or the model in Desktop).
- Remove one column at a time from the query and rerun. Usually one or two high-cardinality columns (IDs, datetime with time, free text) account for most of it.
- Check those columns in DAX Studio under Advanced > View Metrics (VertiPaq Analyzer) to confirm their cardinality.
Then fix those columns specifically: split datetime into separate date and time columns, round timestamps you don't need to the second, and move IDs and long text to a drillthrough page for a single row. Combined with a default filter on the page as benibix described, that usually brings a plain table visual back under the limit.
If this helps, please mark it as the solution.