Cloud & Platform

Data Warehouse Credit Calculator

Monthly and annual cost by warehouse size, with the break-even runtime for every size above and below yours.

Loading the tool…

Processing happens locally in your browser. What you paste or load is processed by this page and is not uploaded to a server. Nothing is stored unless you use a control that says it stores something, and you can clear anything this site has kept from the privacy page.

How to use this tool

  1. Set the warehouse size by name: X-Small through 4X-Large.
  2. Set the active hours per day and days per month. Active means running, not querying — an idle warehouse bills the same.
  3. Put in your contracted credit price rather than leaving the default.
  4. Select Cost the warehouse and read the break-even column before agreeing to size up.

What warehouse credit calculator does

Warehouse sizes double in both compute and price at every step, which produces a rule worth memorising: a bigger warehouse is cost-neutral exactly when it halves the runtime, and a saving only when it does better than that. For a large scan that is genuinely possible. For a query bounded by anything else — a small table, a skewed join, a slow source — it is not, and the bill doubles for no change in wall-clock time.

The table gives the monthly and annual cost for every size, plus the runtime at which each one breaks even against the size you chose, so the argument can be settled with a number instead of an opinion. The credit price is your contracted rate rather than a constant. And if the warehouse is active twelve or more hours a day, check auto-suspend before anything else: an idle warehouse bills exactly the same as a busy one.

Frequently asked questions

Only if it more than halves the runtime, because each size step doubles both the power and the price. A large scan that parallelises cleanly can do that. A query bounded by a small table, a skewed join or a slow external source will not, and the bill doubles for no improvement. The break-even column gives you the exact runtime the argument turns on.

Any hour the warehouse is running, whether or not it is executing anything. A warehouse left on through a quiet afternoon bills identically to one running flat out, which is why auto-suspend is usually the single largest saving available on a warehouse bill and why it is worth checking before any resizing.

Set the cluster count and the cost is multiplied by it, which is the right model for a warehouse pinned to a fixed number of clusters. Auto-scaling between a minimum and a maximum is harder to predict, because it depends on concurrency at each moment — for that, cost the maximum as a worst case and the minimum as a floor, and expect the real figure in between.

On your contract rather than on a public page. It varies by edition, cloud, region and how much you have committed to, and the difference between list and a committed rate is substantial. The default here is a plausible mid-range figure so the tool produces something on first run; it is not a quote.