Welcome to your new dbt project!
- Learn more about dbt in the docs
- Check out Discourse for commonly asked questions and answers
- Join the chat on Slack for live discussions and support
- Find dbt events near you
- Check out the blog for the latest news on dbt's development and best practices
| command | usage |
|---|---|
| dbt --help | Help on CLI |
| dbt init | Initialize a new DBT project. |
| dbt run | To run dbt jobs |
| dbt run --full-refresh --select <model_name> | To run dbt full refresh job for a specified model. The usual dbt run command will fail in case of schema change when we have on_schema_change = 'fail' set on any of the model config. so you must use --full-refresh --select <model_name> arg |
| dbt compile | To complie the project and make sure all references are correct |
| dbt snapshot | To recreate scd type 2 based tablesd defined under snapshots/ |
| dbt test | To run all the tests |
| dbt test --select <model_name> | To run tests associated with selected models |
| dbt seed | To load all the files under seed/ |
| dbt deps | To install third party packages defined in packages.yml |
| dbt docs generate | To generate documentation |
| dbt docs serve | Light weight server to host dbt documentation html site |
| dbt test --select source:.<source_table> | To execute test inside sources.yaml |
| dbt --debug test ... | to run test in a debug mode |
schema.yml file present under models/, is used to define generic and custom generic tests generic tests are the built in tests available in dbt. custom generic tests needs to be defined by you based on customised requirements and can be placed under macros
schema.yml file present at root level, it defines the external packages which help extend dbt functionality. To explore the packages visit hub.dbt.com