- Run command: Use dbt run --select elementary (no special flags needed) to create Elementary’s tables/views. If you’re using a non-default dbt target/environment, include the matching target, e.g., dbt run --select elementary --target prod, so the tables are created where your tests/runs will write data (otherwise you may see “Unable to insert rows to non-existent table”) ([Initial run guidance](https://slack.com/archives/C02CTC89LAX/p1668088517905629); [Target-specific note](https://github.com/elementary-data/elementary/issues/830); [CI/setup notes](https://slack.com/archives/C02CTC89LAX/p1669287068633309); [General “once on install/minor upgrade” guidance](https://slack.com/archives/C02CTC89LAX/p1685412868454149)). - Which user should create the objects: The knowledge sources don’t specify a distinct “elementary user.” They consistently show running dbt run --select elementary within your dbt project and then pointing the edr CLI to that same schema. Practically, run the command with whatever dbt profile/user has privileges to create the Elementary schema/tables in the intended warehouse/database/schema (often your standard dbt deployment user). Ensure the edr CLI profile points to the same location afterwards ([CLI/profile alignment](https://slack.com/archives/C02CTC89LAX/p1679041553593269); [Per-target setup](https://github.com/elementary-data/elementary/issues/830)).