Congrats @John Drummond

Hi @Jolene du Plessis Paginated Reports run on the server, and they're typically more memory-intensive than standard Power BI reports — especially if: - You're working with large datasets - The queries return a lot of rows - The report layout includes nested tables or detailed data regions The F2 SKU is an entry-level capacity with limited memory and processing power, so it's more likely to hit memory limits when rendering paginated reports. On the other hand, Power BI reports usually run just fine because: - They use more efficient DAX queries - They offload some of the work to the client, which helps reduce server memory usage What You Can Do: 1. Optimize the Paginated Report: - Limit how much data the report is pulling - Add parameters to filter the data before it's loaded - Avoid heavy designs like deeply nested tables or repeating data queries - Try to reduce or eliminate things like Lookup functions or embedded custom code 2. Review the Semantic Model: - Remove unnecessary columns or fields - Reduce high-cardinality columns if possible - Consider creating pre-aggregated tables to simplify what the report is querying 3. Consider Upgrading Your Capacity: - Moving to a higher SKU (like F4 or above) gives you more memory and better performance for paginated reports - Here's a helpful link to check the memory limits by SKU:https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-what-is#capacity-nodes

Thanks for sharing Will !!