SQL Tran's static analysis engine maps every reference, every dependency, and every issue across your entire codebase. Instantly.
The usual approach
Translation without understanding produces broken code. Before SQL Tran touches a single line, the static analysis engine builds a complete map of your database: what references what, what depends on what, and what is already broken in the source.
The SQL Tran approach
Static analysis is the pillar of every advanced feature in SQL Tran. It powers accurate translation, dependency mapping, test generation, and issue detection. Without it, you are guessing. With it, you have full visibility.
How it works
After Hummingbird parses your SQL into a syntax tree, the static analysis engine walks the entire codebase and resolves every name reference. It connects tables to the views that query them, procedures to the functions they call, and columns to every expression that reads or writes them.
The analysis is not a one-time scan. It runs continuously as you work, updating the dependency graph in real time as code changes.
What it detects
Objects referencing tables, columns, or procedures that do not exist. Source databases almost always have far more broken code than anyone realizes. SQL Tran surfaces it all.
Code that is never called from anywhere in the database. Dead code adds migration complexity for no value.
Chains of references that are not obvious from reading individual objects. A change in one table can cascade through views, procedures, and functions in ways that are invisible without full-graph analysis.
Features in the source dialect with no direct equivalent in the target. SQL Tran identifies these early so they can be addressed through emulation or manual review.
The Analysis Tab
Press F12 or Ctrl+click any name to jump to the definition of the referenced object. Navigate complex codebases the way you would in a modern IDE.
Hover any name to see what it declares or references. Instant context without switching views.
The Analysis tab shows every object the current one depends on, every object that references it, and every broken reference. In both source and target views.
Key benefits
Start a free assessment and discover every dependency, every broken reference, and every issue hiding in your codebase.