New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
A source added a column last week and nobody told you until a report broke.
What you'll have at the end
A daily check that flags any new, missing, or changed column before the next load runs
You need
A scheduled load that already extracts named columns from one or more specific source tables, with query access to that source system's own catalog views.
Not covered
Ranking a detected change by whether anything downstream actually reads the specific column that moved; that needs column-level lineage across a whole warehouse, and this recipe only scopes the check to the table or tables your own load reads.
Give every load a data quality gate
reach for this once a load's shape is stable and the open question shifts to whether the rows inside it are actually correct, rather than merely well formed.
One bad row keeps taking down the whole nightly load
use this once the schema check passes clean but a single malformed row inside an otherwise normal-shaped batch is what keeps killing the load.
Checked 25 Aug 2026
Part of the ETL (Extract, Transform, Load) cookbook