Procedure Flow — turn SQL into a flowchart

Turn a stored procedure into a flowchart with branches, loops and data lineage. Supports T-SQL, PL/SQL, PL/pgSQL, MySQL and Snowflake. Your SQL is never uploaded.

//🗺️ Procedure Flow

🗺️ Procedure Flow

Paste or upload a stored procedure and see it as a flowchart — branches, loops and error handlers — plus a data-lineage view of the tables it reads and writes. Supports T-SQL, PL/SQL, PL/pgSQL, MySQL and Snowflake. Choose a whole folder of .sql files to search across every procedure by name or table. Runs entirely in your browser — your SQL is never uploaded.

Paste a stored procedure (or upload a .sql file) and see it as a flowchart — branches, loops and error handlers — plus a data-lineage view of the tables it reads and writes. Search within the procedure, or choose a whole folder and search across every procedure in it. Parsing runs entirely in your browser — your SQL is never uploaded.

Search across a folder of procedures

Every file is read and indexed in your browser — nothing is uploaded to the server.

About Procedure Flow — turn SQL into a flowchart

Long stored procedures are difficult to reason about. A thousand lines of nested conditionals, loops and error handlers hides the actual control flow, and the tables a procedure touches are usually scattered across dozens of statements.

This tool parses a procedure and draws it: a flowchart of the branches, loops and handlers, plus a data-lineage view of which tables it reads and which it writes. It understands T-SQL, PL/SQL, PL/pgSQL, MySQL and Snowflake, and detects the dialect automatically.

How to use it

  1. Paste your procedure, or upload a .sql file. You can also point it at a whole folder to search across every procedure by name or by the tables it touches.
  2. Read the flowchart. Conditionals show both arms, loops show their back edge, and error handlers appear as reachable paths rather than being hidden.
  3. Switch to the lineage view to see reads and writes, or the call graph to see how procedures in a folder call each other.
  4. Download the diagram as PNG or SVG for documentation or a review.

Frequently asked questions

Is my SQL uploaded anywhere?
No. The parser runs entirely in your browser, in both the local and public versions. Your SQL never reaches a server, which matters when the procedure is proprietary.
What happens with dynamic SQL?
It is reported rather than guessed at. Where a statement is built at runtime, or an object is named indirectly, the tool lists it in a panel above the chart as something it could not resolve. A chart that quietly omitted these would be worse than one that admits the gap.
Which SQL dialects are supported?
T-SQL (SQL Server), PL/SQL (Oracle), PL/pgSQL (PostgreSQL), MySQL and Snowflake. The dialect is detected from the syntax, including procedures wrapped in quoted bodies.