dbt | Notion

“dbt” is a transformation workflow that helps you complete more work while producing higher-quality results.
You can use dbt to modularize and centralize your analytics code while providing your data team with guardrails typically found in software engineering workflows.
Collaborate on data models, version them, and test and document your queries before safely deploying them to production, with monitoring and visibility.
dbt compiles and runs your analytics code against your data platform, enabling you and your team to collaborate on a single source of truth for metrics, insights, and business definitions.
This single source of truth, combined with the ability to define tests for your data, reduces errors when logic changes and alerts you when issues arise.

dbt optimizes your workflow

Avoid writing boilerplate DML and DDL by managing transactions, dropping tables, and managing schema changes.
- Write business logic with just a SQL select statement or a Python DataFrame that returns the dataset you need, and dbt takes care of materialization.
Build up reusable or modular data models that can be referenced in subsequent work instead of starting at the raw data with every analysis.
Dramatically reduce the time your queries take to run: Leverage metadata to find long-running models that you want to optimize and use incremental models which dbt makes easy to configure and use.
Write less duplicated code by leveraging macros, hooks, and package management.

“dbt” provides a more reliable analysis

No longer copy and paste SQL, which can lead to errors when logic changes. Instead, build reusable data models that get pulled into subsequent models and analysis. Change a model once and that change will propagate to all its dependencies.
Publish the canonical version of a particular data model, encapsulating all complex business logic. All analysis on top of this model will incorporate the same business logic without needing to reimplement it.
Use mature source control processes like branching, pull requests, and code reviews.
Write data quality tests quickly and easily on the underlying data. Many analytic errors are caused by edge cases in the data: testing helps analysts find and handle those edge cases.

The power of dbt

As a dbt user, your main focus will be on writing models (i.e. select queries) that reflect core business logic – there’s no need to write boilerplate code to create tables and views, or to define the order of execution of your models. Instead, dbt handles turning these models into objects in your warehouse for you.

Feature	Description
Handle boilerplate code to materialize queries as relations	For each model you create, you can easily configure a materialization. A materialization represents a build strategy for your select query – the code behind a materialization is robust, boilerplate SQL that wraps your select query in a statement to create a new, or update an existing, relation. Read more about https://docs.getdbt.com/docs/build/materializations.
Use a code compiler.	SQL files can contain Jinja, a lightweight templating language. Using Jinja in SQL provides a way to use control structures in your queries. For example, if statements and for loops. It also enables repeated SQL to be shared through macros. Read more about https://docs.getdbt.com/docs/build/jinja-macros.
Determine the order of model execution.	Often, when transforming data, it makes sense to do so in a staged approach. dbt provides a mechanism to implement transformations in stages through the https://docs.getdbt.com/reference/dbt-jinja-functions/ref. Rather than selecting from existing tables and views in your warehouse, you can select from another model.
Document your dbt project	dbt provides a mechanism to write, version-control, and share documentation for your dbt models. You can write descriptions (in plain text or markdown) for each model and field. In dbt Cloud, you can auto-generate the documentation when your dbt project runs. Read more about the https://docs.getdbt.com/docs/collaborate/documentation.
Test your models	Tests provide a way to improve the integrity of the SQL in each model by making assertions about the results generated by a model. Read more about writing tests for your models https://docs.getdbt.com/docs/build/data-tests
Manage packages	dbt ships with a package manager, which allows analysts to use and publish both public and private repositories of dbt code which can then be referenced by others. Read more about https://docs.getdbt.com/docs/build/packages.
Load seed files	Often in analytics, raw values need to be mapped to a more readable value (for example, converting a country code to a country name) or enriched with static or infrequently changing data. These data sources, known as seed files, can be saved as a CSV file in your project and loaded into your data warehouse using the seed command. Read more about https://docs.getdbt.com/docs/build/seeds.
Snapshot data	Often, records in a data source are mutable because they change over time. This can be not easy to handle in analytics if you want to reconstruct historic values. dbt provides a mechanism to snapshot raw data for a point in time, through use of https://docs.getdbt.com/docs/build/snapshots.