Clouds, DBUs & editions

Databricks · Databricks Fundamentals

Theory

Databricks runs as a managed service on AWS, Azure (as Azure Databricks) and Google Cloud. An account can hold several workspaces, usually one per environment or team, and each workspace is tied to one cloud region. Usage is measured in DBUs (Databricks Units): a normalized unit of processing per hour. How many DBUs a workload consumes depends on the compute type (all-purpose, jobs, SQL, serverless), its size and how long it runs.

For classic compute you also pay your cloud provider for the virtual machines, while serverless usage is billed by Databricks only. Plans (tiers) such as Premium and Enterprise decide which security and governance features you get; the old Standard tier is being retired. For example, a nightly job on job compute for one hour uses fewer DBUs than running the same code on an all-purpose cluster left on all day. Usage is visible in the system.billing.usage system table.

Why we use it

Cost questions come up in every project and in the exam. Understanding DBUs and compute types lets you explain why a job cluster or serverless job is cheaper than an idle all-purpose cluster.

When to use it

Look at DBUs when choosing compute, sizing clusters or reviewing a bill. Use system.billing.usage and the account console usage pages for real numbers. Check current pricing pages for rates; they differ by cloud, region and plan.

How it works

  1. Workload starts on some compute
  2. Databricks meters DBUs by compute type, size and time
  3. Is it classic compute? Yes: You also pay the cloud provider for the VMs. No: Serverless: Databricks bills all of it.
  4. Usage rows land in system.billing.usage
  5. Query or chart the usage to control cost

Syntax

DBU = Databricks Unit (normalized processing per hour)
system.billing.usage (usage_date, sku_name, usage_quantity, ...)
Account console → Usage

Example

-- DBUs per product per day, last 30 days
SELECT usage_date,
       sku_name,
       SUM(usage_quantity) AS dbus
FROM system.billing.usage
WHERE usage_unit = 'DBU'
  AND usage_date >= current_date() - INTERVAL 30 DAYS
GROUP BY usage_date, sku_name
ORDER BY usage_date, dbus DESC;

Key points

Databricks topics

Databricks Fundamentals

Compute

Notebooks & Development

Apache Spark on Databricks

Delta Lake

Unity Catalog & Governance

Data Ingestion

Declarative Pipelines (Lakeflow)

Lakeflow Jobs

Databricks SQL & BI

Architecture, Performance & Cost

Machine Learning & AI

Certification & Interview

T
Tech Town
Log InSign Up Free
Home SQL Python DSA Power BI Snowflake Databricks Spark Gen AI Practice Problems Contest Blog

Master Databricks

The lakehouse platform from the ground up: Apache Spark, Delta Lake, Unity Catalog, Lakeflow pipelines and jobs, Databricks SQL and MLflow. Click any topic in the sidebar to open it right here.

{{ sectionCount }}
Sections
{{ topicCount }}
Topics
Free
Forever
Hands-on practice Practice SQL / Spark SQL Sharpen the SQL you use in Databricks SQL and Spark SQL: 150 query problems in a live editor with instant checking. Start practising →
Section {{ sec.num }}

{{ sec.label }}

Databricks  /  {{ current.sectionLabel }}  /  {{ current.name }}

{{ current.name }}

Theory

{{ current.def }}

Why we use it

{{ rich.why }}

When to use it

{{ rich.when }}

{{ sec.h }}

{{ sec.body }}

{{ sec.body }}

Diagram

{{ rich.dg.caption }}

{{ tb.title }}
{{ c.v }}
{{ rich.dg.op }}
➜
{{ rich.dg.output.title }}
{{ c.v }}
{{ nd.label }}
{{ nd.sub }}
{{ nd.label }}
{{ nd.sub }}
{{ rich.dg.left.title }}
{{ it }}
{{ rich.dg.right.title }}
{{ it }}
On screen — where to click

{{ rich.ui.title }}

{{ u.text }}
  1. {{ st.n }}{{ st.text }}
{{ rich.ui.title }}
{{ u.text }}
Flowchart — how it works
{{ nd.text }}
{{ nd.text }}
◇ {{ nd.text }}
Yes → {{ nd.yes }}
No → {{ nd.no }}
Syntax
{{ current.syntax }}
Example
{{ current.example }}
Want to run this yourself? Databricks needs a real workspace — there's no in-browser engine for it. Click Copy above, then paste it into a notebook or the SQL editor in Databricks Free Edition (free, no credit card) and run it on serverless compute.
Key Points — click to check off as you learn
  • {{ pt.mark }} {{ pt.text }}

Share this topic