Documentation

SQLise · Data lineage from your SQL

SQLise documentation

SQLise is a multi-dialect SQL lineage workspace built around three primitives — Parse, Trace, and Explain. Upload SQL/DDL files or paste SQL directly, and SQLise parses object definitions, identifies relationships with Column Trace™, and renders an interactive lineage graph where each database.schema layer is color-coded.

SQL Server
Snowflake
PostgreSQL
MySQL
Oracle

Supported SQL Objects & Features

Object Types
CREATE TABLE
Column definitions, constraints, FK references
CREATE VIEW
SELECT with FROM/JOIN, column-level lineage
MATERIALIZED VIEW
Tracked like views with dependency detection
PROCEDURE / FUNCTION
Body parsed for table references
STAGE / STREAM
Snowflake stage and stream objects
PIPE / TASK / SEQUENCE
Snowflake pipeline objects
TRIGGER
Trigger definitions with table references
PACKAGE / PACKAGE BODY
Oracle package body dependency tracking
SYNONYM / DB LINK
Alias and cross-database link objects
Dependency Detection
FROM / JOIN
Direct table references in queries
INSERT INTO / MERGE INTO
Write-target tracking
UPDATE / DELETE
DML target detection
CALL / EXEC
Procedure call references
Function calls
Inline function invocations
COPY INTO @stage
Snowflake stage data flow
FOREIGN KEY
Constraint-based lineage
INHERITS
PostgreSQL table inheritance
Schema prefixes
db.schema.table fully qualified names

Column Trace™ — Column-Level Lineage

When a view references columns using alias.column syntax (e.g., o.order_id,c.first_name AS customer_name), Column Trace™ traces which source table columns map to the view's output columns.

Select a view node to see the "Column Trace™" section in the details panel. Each mapping shows source_column → target_column, grouped by source table. This also works through function expressions (e.g., SUM(d.quantity)).

For impact analysis, Impact Graph™ flips the direction and shows everything downstream of a chosen column, table, or view — useful before shipping a schema change. For natural-language explanations of any node, use Query Lens™ from the details panel.

Schema Color Coding

Each unique database.schema combination is automatically assigned a distinct color. Colors persist across sessions. Click the color swatch in the legend to customize any schema's color using the built-in color picker.

Node Shapes by Type

Different SQL object types are visually distinguished by their node shape:

TBL
Table

Sharp corners (rectangular)

VW
View

Rounded corners

FN
Function

Pill shape (fully rounded)

SP
Procedure

Dashed border

STG
Stage

Cloud shape indicator

STR
Stream

Stream indicator

TRG
Trigger

Trigger indicator

SEQ
Sequence

Sequence indicator

How to Use

1. Upload Files or Paste SQL
Drag and drop .sql or .ddl files onto the upload area, click to browse, or paste SQL directly in the quick-start textarea on the landing page. The dialect is auto-detected using keyword scoring, or you can select it manually.
2. Parse & Visualize
Uploaded files are parsed automatically. Pasted SQL uses the "Visualize Lineage" button. The parser uses a two-pass approach: first to identify objects and basic edges, then to resolve complex cross-references across files.
3. Explore the Graph
Zoom with scroll wheel or toolbar controls
Pan by clicking and dragging the canvas; drag nodes to reposition
Click a node for details: columns, column lineage, SQL, upstream/downstream
Hover to highlight connected lineage; click to persist highlight
4. Customize & Export
Customize schema colors using the built-in color picker
Add draggable text annotations with rich formatting options
Export as SVG (vector), PNG (image), or JSON (data)
Save projects with custom names, organize in folders — zoom, pan, node positions, and hidden nodes are all preserved
Auto-save drafts preserve unsaved work automatically, including your current view state

Subscription Tiers

Parse limits are enforced based on your subscription tier. All visualization features (zoom, pan, export, annotations, colors) are available on every tier.

Explorer

50 objects per parse, 5 saved projects

1 draft (1-day retention)

Builder

500 objects per parse, 50 saved projects

3 drafts (7-day retention, 3-min auto-save)

Architect

2,000 objects per parse, 500 saved projects

5 drafts (30-day retention, 2-min auto-save)

Enterprise

30,000 objects per parse, 2,000 saved projects

10 drafts (indefinite retention, 1-min auto-save)

Details Panel

Click any node to open the details panel showing:

  • Object info — Name, type, schema, database, source file
  • Columns — Column definitions with data types (for tables)
  • Column Trace™ — Source-to-target column mappings (for views)
  • SQL Source — Truncated source SQL of the object
  • Lineage & Impact — Upstream/downstream nodes split into Direct (clickable) and Indirect, with totals and schema/type breakdowns

Known Limitations

  • Complex nested subqueries may not be fully traced
  • Dynamic SQL (EXEC/sp_executesql) string content is not parsed
  • Column-level lineage requires alias.column syntax in SELECT clauses
  • Cross-database references require all schemas in uploaded files
  • CTEs referenced outside the immediate WITH block may not resolve