Skip to content
Finitizer

BigQuery FinOps Query Pack

Copy ready-made SQL for the common BigQuery cost questions, with notes on how to read each result.

Google CloudReference60 seconds

24 recipes · 19 of them read only metadata and cost a fraction of a cent.

New here? See what this tool does and how to use it.

Learn more

BigQuery FinOps Query Pack

What this free tool does for you

When the BigQuery bill jumps, answer "what is driving it?" fast with ready-made SQL: the costliest queries, tables nobody uses, cost by team. Most of it costs under a cent to run.

How to use it

  1. Find your question in the list. Recipes are grouped into query cost, slots, storage and billing export.
  2. Check the badge: Under a cent to run reads only metadata; Scans billing data reads your billing export, so it costs more.
  3. Open the recipe, choose your region or dataset in the picker, and copy the SQL.
  4. Run it in the BigQuery console, then use the notes on the same page to read the result.

Good to know

  • Query failed? The usual cause is a region or dataset mix-up. The picker on each recipe fills in the right one.
  • Billing export recipes. They query a real table, so filter on its partition column before you run one to keep the cost small.
Region or dataset qualifier? JOBS, JOBS_TIMELINE and TABLE_STORAGE need a region (`region-us`). COLUMNS and TABLE_OPTIONS take a region or a dataset. With a dataset they see that one dataset only, so these recipes use the region and check every dataset in it. A wrong qualifier is a common reason a copied INFORMATION_SCHEMA query fails. Every recipe here has a picker that fills it in.

Query cost & performance

Slots & reservations

Storage

Billing export

Why metadata queries cost almost nothing

INFORMATION_SCHEMA views are served from BigQuery’s metadata, not from your table data. They are still billed like any query: on demand there is a 10 MB minimum per query and the results are never cached, so every run is charged. A month of job history is usually megabytes, which is a fraction of a cent, and inside the monthly free tier for most projects. That is why “Under a cent to run” marks them here. The billing-export recipes are the exception: they query a real table, so filter on the partition column before you run one.

Want this done on your real bill?

BigQuery Cost Guardrails Setup: We set safe limits on every BigQuery project so one runaway query cannot cost thousands. From $1,500, fixed. Nothing paid upfront.

See the service

Related tools

More tools for: Analytics and warehouses, Billing data, allocation and governance

These are the questions. Finitizer keeps the answers current.

Running twenty-four queries by hand once is a good afternoon. Finitizer runs the equivalent continuously across BigQuery, GCP, and AWS, tracks how each number moves between runs, and turns the findings into assigned tasks or a Terraform PR.

See how Finitizer works

Rate this tool

How would you rate the BigQuery FinOps Query Pack?