Senmi Rai
03/09/2026, 3:56 PMkapa.ai
03/09/2026, 3:56 PMdbt run / test / build):
◦ elementary_test_results – results of all dbt tests
◦ dbt_run_results – results of all dbt executions
• When Elementary models are explicitly run (dbt run --select elementary):
◦ dbt_models, dbt_tests, dbt_sources, dbt_exposures, dbt_metrics – project metadata and configuration
Artifact Tables
Elementary organizes artifacts into two categories: [dbt artifacts]
| Category | Tables |
| - | - |
| Metadata tables | dbt_models, dbt_tests, dbt_sources, dbt_exposures, dbt_metrics, dbt_snapshots, dbt_seeds, dbt_columns, dbt_groups |
| Run results tables | dbt_run_results, dbt_invocations, elementary_test_results, model_run_results, snapshot_run_results, seed_run_results, job_run_results, dbt_source_freshness_results |
When to Run dbt run --select elementary
• When you first install Elementary in an environment (to create the tables)
• When you upgrade to a new minor version of the Elementary package (schema changes)
• When you make changes to your dbt project structure (to refresh metadata tables)
Outside of these cases, the on-run-end hooks handle keeping results up to date automatically.
Controlling Artifact Uploads
You can disable specific uploads using variables in `dbt_project.yml`:
vars:
disable_dbt_artifacts_autoupload: true # disables metadata table uploads on-run-end
disable_dbt_invocation_autoupload: true # disables invocation metadata uploads
disable_run_results: true # disables run results uploads
disable_tests_results: true # disables test results uploads
[on-run-end hooks; dbt artifacts]
> Note: Elementary recommends not disabling the on-run-end hooks for environments you want to monitor, as reports and alerts rely on them being up to date. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.