Why dbx-sql-runner?
DBT is powerful, but often overkill for modern Databricks.
When you're running on Databricks with Unity Catalog, you already have:
- ✅ Built-in Metadata Management (Unity Catalog)
- ✅ Automatic Data Lineage
- ✅ Robust SQL support
dbx-sql-runner strips away the complexity. It gives you just what you need: a lightweight DAG runner for your SQL files, environment management, and essential tooling like linting and alerting. No heavy adapters, no jinja-hell, just SQL.
Minimalist & SQL-First
Just write .sql files. No complex boilerplate or excessive configuration. Designed for Databricks SQL where Unity Catalog already handles metadata and lineage.
Library-First Design
Not just a CLI. Import dbx_sql_runner in your Python scripts. Perfect for orchestrating transformations within Airflow or Databricks Jobs.
Built-in Tooling
Comes with a built-in Linter (via Ruff) to enforce code quality and Alerting webhooks to notify you of run status.