Result Caching in Snowflake
Result Caching means Snowflake stores the final result set of a query in the cloud services layer. If the same query is executed again within 24 hours (and data hasn’t changed), Snowflake reuses the cached result instantly — no warehouse needed, no extra cost.
🔹 How It Works (Step by Step – Top to Bottom)
1️⃣ User Runs a Query Snowflake receives a SQL query for execution.
2️⃣ Check Result Cache Snowflake looks in the Result Cache to see if the exact same SQL has already been executed recently.
3️⃣ Cache Hit (Reused)
-
If the query already exists in cache (identical SQL, same role/session context, unchanged data):
- Snowflake returns the stored result instantly.
- No warehouse spins up → 0 credits consumed.
4️⃣ Cache Miss (Not Found)
-
If the query is new or data has changed:
- Snowflake uses the warehouse to run the query.
- The result set is then stored in the Result Cache for 24 hours.
5️⃣ Next Execution (Reuse)
-
If the same query is run again within 24 hours:
- Snowflake skips re-execution.
- Cached result is reused → response is instant.
🔹 Example
SELECT COUNT(*)
FROM SALES_TRANSACTIONS
WHERE TRANS_DATE = '2025-09-01';
- First Run → Warehouse executes query → Result stored in cache.
- Second Run (same SQL) → Snowflake returns cached result instantly, warehouse not used.
🔹 Visual Flow (Result Cache Only)
🔹 Key Points
- ✅ Stored in cloud services layer (not tied to warehouse).
- ✅ Valid for 24 hours.
- ✅ Shared across users, sessions, and roles (if permissions allow).
- ✅ Zero warehouse cost when reused.
❌ Not used if:
- SQL text is different.
- Underlying data has changed.
- Query uses non-deterministic functions (
NOW(),RANDOM()).
👉 In short: Result Caching = save final query results → reuse later for instant performance + zero cost.