KivTools

SQL Lineage & Impact Analyzer

Trace table, column and JOIN dependencies across SQL, CTEs, views and MERGE. Import SQL or dbt projects and analyze them locally in your browser.

LOCAL ONLY Column Lineage Static Analysis
Your SQL, schema and uploaded files are analyzed inside this browser. KivTools does not upload them for lineage analysis.
INPUT

Input workspace

Preparing local SQL engine…
No files selected Drop SQL, ZIP or dbt files here

Choose the actual SQL dialect when known for more accurate parsing.

OUTPUT

Lineage graph

Waiting for analysis
Export

Trace a column from source to output

Load the example or paste SQL, then analyze it with the local SQLGlot engine.

Direct Transformation Context

Details

Select a node in the graph

Node details, SQL fragments and text lineage paths appear here.

Downstream impact

Deterministic paths

Select a source column to count affected columns, views and final results.

SQL LINEAGE

Trace SQL dependencies before changing a query

Column lineage follows source columns through expressions, CTEs and views to each output. Impact analysis reverses those paths to show what a source change can affect.

What this analyzer resolves

SELECT, aliases, JOIN, subqueries, CTEs, UNION, aggregates, window functions, QUALIFY, MERGE, CREATE VIEW, CTAS and INSERT SELECT.

When schema information helps

CREATE TABLE definitions improve SELECT * expansion, ambiguous-column resolution and qualification.

Static-analysis limits

Dynamic SQL and stored procedures may be incomplete. Runtime database behavior is never executed.

FAQ

What is SQL column lineage?

It maps each output column back through transformations to the source columns that produced it.

Does KivTools upload my SQL?

No. SQL, schema and selected files are parsed inside this browser for lineage analysis.

Why should I provide table schema?

Schema definitions help expand SELECT *, qualify columns and resolve ambiguous names.

Can it analyze CTEs and views?

Yes. Supported CTEs, views and multi-statement dependencies are followed through the local source catalog.

Can it analyze dynamic SQL?

Only partially. Dynamic SQL often depends on runtime values that static analysis cannot resolve.

Recent tools: