Use Case: SQL Debugging

Debug SQL Faster with Visual Lineage

Duplicated rows, wrong aggregations, broken joins — Column Trace™ shows you the bug in seconds, not hours.

Most SQL bugs are not syntax bugs. They are 'the number is subtly wrong' bugs. The fastest way to find them is to see the path the wrong number took.

The pattern: numbers that double

Two child tables both fan out from the same parent, and a SUM downstream multiplies the rows. The lineage graph makes this visible immediately — both child tables connect to the same projected column.

The pattern: silently wrong GROUP BY

A column missing from GROUP BY in a relaxed dialect picks an arbitrary value. Visual lineage shows that the offending column comes from a non-grouped table, which is your hint.

Workflow

1. Paste the failing view. 2. Click the wrong column. 3. Inspect the upstream tables. 4. Pre-aggregate the fan-out. 5. Re-paste and confirm the lineage.

What it looks like

Spot the join that exploded your row count.

Explorer handles most one-off debugging sessions (50 objects per parse). Builder and above keep your saved projects so the next debugging session starts where you left off.

Frequently asked

Do I need to install anything?

No. The debugging workflow runs entirely in the browser. Paste SQL and go.

Can I share the debug session with a teammate?

Yes. Generate a share link from the diagram and your teammate sees the same lineage in their browser.

Drop your SQL in and find the bug

Free, no sign-up.

Why your SQL is duplicating rows SQL GROUP BY mistakes Examples