Memory issue

Hi PBI_2K26,

On the limit: the capacity setting Query Memory Limit (%) (Admin portal > Capacity settings > your capacity > Power BI workloads) can only lower the memory one query may use, not raise it above what the SKU allows. On F64 that ceiling is 10 GB, so the only way past it is a larger SKU.

Why a plain table hits it: with only columns, the visual still groups by every column combination across the 600M rows and sorts the result to find the first rows to show. Every extra high-cardinality column (IDs, timestamps, free text) multiplies that work. The few hundred rows you see are cheap. The full grouping behind them is what uses the memory.

Ways to keep one visual:

1. Don't let it run unfiltered. Add a visual-level filter or a slicer (date range, region) that is always set, so the grouping only covers a slice.
2. Drop or move the widest columns. Remove IDs and long text from the table and show them on a drillthrough page for one row.
3. Sort by a column people actually need. Sorting by a unique ID or a timestamp forces a sort over everything.
4. For real row-level lists at this size, use a paginated report on the same model, or a DirectQuery detail table to Snowflake in a composite model. Both are made for long lists. An Import table visual isn't.