Question

An analytics team enables the Search Optimization Service on a 5 TB table that receives frequent bulk inserts throughout the day. After a week, the finance team notices unexpected credit consumption even during periods when no queries are running against the table. What is the MOST likely cause of the ongoing cost?

Accepted Answer

The search access path (search optimization data structure) is being automatically maintained by serverless compute as new rows are inserted

Answer

The result cache is being continuously refreshed for the table's queries

Answer

The virtual warehouse assigned to the table cannot auto-suspend while search optimization is enabled

Answer

Metadata cache regeneration consumes credits each time the table changes