Getting Started¶

Follow these three steps to start analysing your SQL scripts with Gudu SQLImpact.

1. Download the JAR¶

Grab the latest gudu-sqlimpact.jar from the Download page.

Place your SQL files in a directory. Nested folders are fine; wildcards are supported.

project/
 ├─ schema/
 │   ├─ create_tables.sql
 │   └─ alter_tables.sql
 └─ data/
     └─ load_data.sql

java -jar gudu-sqlimpact.jar \
  --dialect postgres \
  --in project/ \
  --summary \
  --out report/summary.json

--dialect – Database dialect of the SQL to parse.
--in – File or glob pattern to analyse.
--summary – (Optional) Produce aggregated view instead of per-statement detail.
--out – Output file path.

When the command finishes you will find summary.json ready for inspection.

For Windows users, use the following command in Command Prompt (cmd.exe). Note the caret (^) is used for line continuation instead of backslash:

java -jar gudu-sqlimpact.jar ^
  --dialect mssql ^
  --in project/ ^
  --summary ^
  --out report/summary.json 