Explanation
Why the waste happens and who it affects.
By improving lookup efficiency, it allows smaller warehouses to satisfy performance SLAs, reducing credit consumption.
However, inefficiencies arise when:
- Search Optimization is not enabled on critical lookup-heavy tables, forcing oversized warehouses.
- It is enabled unnecessarily on infrequently queried data, adding avoidable costs.
- Warehouse sizing is not adjusted after Search Optimization is implemented, missing the primary cost-saving opportunity.
Regular review of query patterns and warehouse sizing is essential to maximize the intended benefit of Search Optimization.
Billing model
The pricing dimensions that drive this cost.
- Storage - the search access path is billed as Snowflake storage; it is typically about one quarter of the table size, depending on the number of distinct values and the data types
- Serverless compute - building and maintaining the search access path consumes Snowflake-managed compute credits, and maintenance cost rises with table churn (large volumes of inserts, updates, and deletes)
- Warehouse credits - queries still run on the user's virtual warehouse; Search Optimization saves money only when it lets lookup-heavy workloads run on a smaller warehouse or for less time
- Use `SYSTEM$ESTIMATE_SEARCH_OPTIMIZATION_COSTS` to estimate costs before enabling it (actual costs can differ from the estimate), and the `SEARCH_OPTIMIZATION_HISTORY` view to track credits consumed
How to detect
4 checks to find it in your estate.
- Identify tables where Search Optimization is enabled and assess actual query usage patterns on optimized columns.
- Detect cases where Search Optimization is enabled but query volume against the indexed columns is low.
- Identify workloads that experience point-lookup query latency but operate on oversized warehouses without Search Optimization.
- Evaluate if warehouses supporting lookup-heavy workloads remain oversized despite Search Optimization being available.
How to fix
4 ways to remove the waste.
- Enable Search Optimization selectively on columns supporting frequent, high-value point-lookup queries
- After enabling Search Optimization, reassess and right-size warehouses where feasible.
- Remove Search Optimization from tables or columns with low query activity to eliminate unnecessary storage and maintenance costs.
- Periodically audit Search Optimization configurations against evolving workload patterns and business needs.
Documentation
Vendor references for pricing and configuration.