proc>flow

Four dialects of SQL, one flowchart

🔒 Local only

Your SQL stays in this browser. Procflow does not upload SQL, connect to a database, or send it to an API. Imported files remain in this tab and are discarded when it closes. Workspace persistence is opt-in: nothing is saved to this browser unless you choose Save in the Workspace menu, and saved workspaces are local-only, exportable, and clearable.

SQL source Object Dialect

Confidence—

Coverage—

Diagnostics0

Constructs—

Cyclomatic complexity1

Paste some SQL to see how many paths a reader would have to walk.

Scope Direction Detail View

View settings

Group straight runs Number the steps Error path per step Source tables

Catalogue

Paste or import table/view/column metadata so unresolved object references resolve to their exact identity instead of an external label.

Catalogue

No catalogue loaded.

Reports

Paste or import an SSRS/RDL report definition so its datasets link to their SQL analysis. Embedded, shared, and unresolved datasets are distinguished, and each embedded dataset's query can be opened and analysed from the Dataset picker.

Report definition (RDL/XML)

Dataset

No report definition loaded.

Export

Workspace

Filter dependencies

Filters affect the dependency view only; the analysis graph is unchanged.

Reads Writes Calls External objects Temp tables Focus

Filter report

Filters affect the report view only; the analysis graph is unchanged.

Columns Embedded datasets Shared datasets Unresolved datasets External objects Focus

Paste SQL on the left. The flowchart updates automatically as you work.

flowchart TD

Parsing is heuristic, not a compiler. Dynamic SQL is opaque to any static eye, and semicolon-free batches may bend the picture. Trust it as a map, not as the territory.