Use Case: Impact Analysis

SQL Impact Analysis Before You Ship

Renaming a column, dropping a table, or refactoring a view? See every downstream object that depends on it — at the column level — before you touch production.

A 'simple' rename in a base table can break six dashboards and three pipelines. Object-level dependency lists hide which downstream columns will actually break.

Downstream impact in one click

Click any node and the details panel shows direct + indirect downstream objects, broken down by schema and type. Click a column and you see only the downstream columns affected.

Before/after comparisons

Save the current lineage, make your change, and re-parse. The two diagrams sit side by side as separate projects so you can compare what changed.

What it looks like

customersv_customers_cleanv_active_customersmart_revenuemart_churn
See every downstream object before you change a column.

Builder and above raise saved-project limits so you can keep before/after snapshots for every refactor.

Frequently asked

Can it analyze a multi-file project?

Yes. Upload several .sql / .ddl files at once. Cross-file references are resolved during the second parse pass.

Will it tell me which dashboards break?

It tells you which downstream SQL objects break. Dashboard mapping is on the roadmap; today you can export the impact list as JSON.

See the downstream impact of your next change

Paste DDL → click → see what breaks.

Related