A Snowflake bill can double when warehouse runtime, warehouse size, concurrency, serverless usage, storage, or transfer volume changes.
Start with daily totals in METERING_DAILY_HISTORY, then compare warehouse credits in WAREHOUSE_METERING_HISTORY with query activity in QUERY_HISTORY. A change in warehouse hours or size usually points to compute. A change in service type points to Snowpipe, clustering, search optimization, Cortex, or another serverless feature.
Common causes include a job running more often, a warehouse serving new workloads, a larger warehouse, additional clusters, longer idle intervals, and a new retention or replication policy. The underlying SQL may remain unchanged while its schedule or concurrency changes.
Compare the bill with the same period in the previous month and record the first date of the increase. Query history and warehouse event history can then show whether the change came from workload volume, configuration, or a new service.