dbt run -s elementary

(or

dbt run --select elementary

) builds/updates the Elementary dbt package models in your warehouse. In practice, you use it: 1. On first installation per environment To create the Elementary tables (the “Elementary schema”) in each env like dev/stage/prod. [[FAQ](https://docs.elementary-data.com/oss/general/faq); [Slack summary](https://elementary-community.slack.com/archives/C02CTC89LAX/p1677879115067759)] 2. When upgrading the Elementary dbt package (minor version changes) A minor version bump can change table schemas, so you rerun it to apply those schema changes (e.g. new columns). [[Release 0.8.0](https://docs.elementary-data.com/oss/release-notes/releases/0.8.0); [Upgrade guidance](https://elementary-community.slack.com/archives/C02CTC89LAX/p1685412868454149)] 3. Optionally in CI/CD to always keep schemas aligned with the package version Some teams run it on deploy/merge, but it’s not required on every daily job as hooks populate the tables. [[CI usage](https://elementary-community.slack.com/archives/C02CTC89LAX/p1690204071561329); [Prod workflow](https://elementary-community.slack.com/archives/C02CTC89LAX/p1741272625948369)] 4. Not needed for every dbt run/test/report Once the tables exist and match the package version, regular `dbt run`/`dbt test` plus the

on-run-end

hooks keep them populated; you don’t need to run

-s elementary

before each

dbt test

or report. [[On-run-end hooks](https://docs.elementary-data.com/dbt/on-run-end_hooks); [Selector question](https://elementary-community.slack.com/archives/C02CTC89LAX/p1711543686145199)] Running it more often is safe (no data loss), just usually unnecessary. [[Daily runs](https://elementary-community.slack.com/archives/C02CTC89LAX/p1687967765734029); [Pipelines](https://elementary-community.slack.com/archives/C02CTC89LAX/p1761811069269149)]

To only send the report to Slack (no GCS upload, no website update), drop all GCS-related flags and

--report-url

and keep just the Slack options, as shown in the Slack “share via Slack” docs.[\[Share via Slack\](https://docs.elementary-data.com/oss/guides/share-observability-report/share-via-slack)] Here’s the edited command:

bash edr send-report \   --env prod \   --profiles-dir . \   -t elementary-prod \   -ch "data-reporting" \   -st {{ ELEMENTARY_SLACK_TOKEN }}

This will send the HTML report as an attachment to Slack, with the default summary included.