Workload Cost Field Guide

Questions to ask before you move your workload

Start with the billing rules, storage you keep and access you need. These questions grew out of the saved engineering discussions; the sources explain what we can and can’t answer.

A fair question

What will it really cost to move?

We can explain how the bill works. We can’t price the migration labor, code changes or day-to-day work from these sources. We also haven’t measured query speed or a full year of costs for your workload.

What goes into a workload quote →

1. How do intermittent BI bursts affect minimum billing windows?

Billing granularity and minimum duration are separate. Snowflake charges a 60-second minimum on every warehouse start or resume; Fabric lists a 1-minute minimum. Firebolt and Databricks describe per-second billing; that alone does not establish their minimums. Ask for an idle-suspend example using your query schedule.

2. What is the real storage multiplier (compression, Time Travel, snapshots, backups)?

Snowflake charges compressed TB plus Time Travel and 7-day Fail-safe on permanent tables; Oracle bills Exadata storage in 1 TB increments plus separate backup storage; Dremio queries customer object storage without markup.

3. Can external engines read and write our Iceberg tables without lock-in fees?

Snowflake storage docs note class 1/2 HTTP request fees when external engines access Snowflake-managed Iceberg tables via Horizon Catalog; Databricks UniForm provides read-only Iceberg access from Delta tables without rewriting Parquet files.

← Return to native-unit overview