Microsoft Fabric Data Warehouse now has result set caching generally available. For a report that repeatedly asks the same analytical question, this can avoid doing the full computation every time. The feature is useful, but it is not a universal speed switch: only eligible queries can create or reuse a cached result, and data changes invalidate earlier results.
What the cache does
A qualifying SELECT query can persist its final result set. When the same query runs again against the same item, Fabric can return that result rather than repeat compilation and data processing. This can help dashboards and reports whose visuals issue recurring aggregations over large tables. Cache management is automatic, and Fabric evicts entries as needed.
Microsoft lists result set caching as enabled by default for Fabric Warehouses and Lakehouse SQL analytics endpoints. You can check the current item setting with:
SELECT name, is_result_set_caching_on
FROM sys.databases
WHERE database_id = DB_ID();
That setting does not promise a hit for every query. Eligibility rules filter out many cases. For example, a query must reference a distributed table with at least 100,000 rows, and its estimated result must be no more than 10,000 rows. Cross-item queries, temporary tables, explicit transactions, non-deterministic functions such as GETDATE(), and queries using row-level security are among the documented exclusions.
Prove a hit before claiming a performance gain
Run the same representative query twice with unchanged source data. In the query editor message output, look for “Result set cache was used.” You can also inspect Query Insights:
SELECT result_cache_hit, command, submit_time
FROM queryinsights.exec_requests_history
ORDER BY submit_time DESC;
The result_cache_hit value is 1 when that execution creates a cache entry, 2 when it uses one, and 0 when the query is not applicable. A useful validation compares the cold run with subsequent warm runs and records the same query text, item, permissions, and data state. Avoid treating one faster execution as proof: service load and other cache layers can affect timings too.
Keep report behavior predictable
Changes to referenced tables invalidate earlier results so users do not keep seeing stale data. Reuse also depends on the query remaining equivalent: different output columns, column order, aliases, connection context, or a cache unused for 24 hours can prevent reuse. If a query is unexpectedly ineligible, check its plan and SQL shape against the documented criteria before redesigning the report.
For a controlled A/B comparison, run the query with result set caching disabled at query level, then compare it with the normal execution. Fabric documents the DISABLE_RESULT_SET_CACHE hint for this purpose. Keep the comparison bounded and repeat it under similar conditions; query latency can vary independently of caching.
Where it fits in a Power BI solution
Caching is most relevant when Power BI or another client submits repeated, eligible T-SQL reads to a Fabric Warehouse or Lakehouse SQL analytics endpoint. It does not replace model design, efficient measures, sensible visual counts, or a performance check from the report side. Start with queries that are both expensive and frequently repeated, confirm cache hits, and measure the end-to-end experience users care about.
The practical takeaway is simple: result set caching can reduce repeated warehouse work without application changes, but the hit indicators and eligibility criteria should be part of validation. Treat it as a workload optimization to measure, not a blanket guarantee for every visual or refresh.