@kapa.ai tell me more about the Elementary tables and views

New message text here

@kapa.ai names and descriptions of all the tables ?

Based on the knowledge sources available, here are the Elementary tables with their names and descriptions: Metadata Tables (Populated when running

dbt run --select elementary

) [dbt artifacts] Run Results Tables (Populated automatically via on-run-end hooks) [dbt artifacts] Anomaly Detection Tables & Views [package models] > Note: The knowledge sources do not provide full descriptions for all tables (e.g.,

dbt_columns

,

dbt_groups

,

dbt_snapshots

,

dbt_seeds

,

seed_run_results

). The above descriptions are directly supported by the available documentation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai what does the artifacts hook do and what table does it stop updating ?

The artifacts hook (part of Elementary's

on-run-end

hooks) automatically uploads your dbt project metadata to the Elementary schema at the end of every

dbt run / test / build

. Specifically, it extracts data from dbt's

graph

object and runs SQL queries to update the metadata tables. [on-run-end hooks] What it updates The artifacts hook updates these metadata tables: [dbt artifacts] •

dbt_models

•

dbt_tests

•

dbt_sources

•

dbt_exposures

•

dbt_metrics

•

dbt_snapshots

•

dbt_seeds

•

dbt_columns

•

dbt_groups

Each time these models run, their data is fully replaced with the current state of your project graph. How to disable it You can stop the artifacts hook from running automatically by adding this to your `dbt_project.yml`: [on-run-end hooks]

vars:
  disable_dbt_artifacts_autoupload: true

Important: what it does NOT affect Setting

disable_dbt_artifacts_autoupload: true

only stops the metadata table updates listed above. It does not stop the upload of: [reduce on-run-end time] •

elementary_test_results

(test results) •

dbt_run_results

(model execution results) •

dbt_invocations

(invocation metadata) Those are controlled by separate variables (

disable_run_results

,

disable_tests_results

,

disable_dbt_invocation_autoupload

). When to manually refresh artifacts If you disable autoupload, you should manually run the artifacts models whenever your project structure changes (e.g., on deploy): [reduce on-run-end time]

dbt run --select elementary.edr.dbt_artifacts

👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.