Clients ask me the same three questions all the time:
- What are system tables?
- What are they about?
- And what can I actually do with them?
I recently came across a Databricks blog that answers the last one brilliantly: Top 5 System Table Queries for Understanding Your Databricks Costs. So here's the simple version first. Then go and read it.
The short answer
Your Databricks invoice is the total on your card bill. System tables are the statement behind it: every line, every date, every shop.
They're read-only tables that Databricks fills in for you, in a catalog called system. You query them like any other table, with SQL, a dashboard or Genie.
What's in them
They cover more than cost. Think of them as a building's logbooks:
- Billing: what you used, and what it costs
- Access: who opened which door (the audit log)
- Compute and jobs: which machines ran, what ran on them, and whether it worked
For cost, two tables do the heavy lifting:
- system.billing.usage is the statement: what was used, how much, and when.
- system.billing.list_prices is the price tag. Usage is counted in DBUs, not pounds, so you need both.
What you can do with them
The blog gives ready-made SQL for five questions:
- Where's the money going? Spend by product, day by day.
- Which warehouse is the big spender? And is it growing?
- Which team spent it? Like name labels in a shared fridge, this only works if people label things.
- Was yesterday weird? Like a smart meter telling you the heating was left on.
- Where will we land this quarter? A forecast built on your own history.
I won't repeat the SQL. That's what the blog is for.
Four gotchas
- Usage isn't money. Multiplying units by the price list gives you the list price, which may not be your negotiated rate.
- It only covers Databricks. On classic compute, the bill for the cloud provider's machines and storage sits somewhere else.
- No label, no owner. Untagged spend shows up as "untagged", and that number is the size of your gap.
- Free to read, not free to run. The tables cost nothing, but the warehouse that queries them does. You may also need an admin to give you access.
Why it matters
One finance team I worked with had all its costs in one unmarked pile. Every budget meeting started with an argument. Once they could see the statement, the meeting started with "here's the line, who owns it?"
Now go and read the blog: Top 5 System Table Queries for Understanding Your Databricks Costs
What's the first question you'd ask your Databricks statement?