Your SSIS packages, finally documented — and diffed before you deploy.

SSIS packages are a black box until someone opens them.

Most SSIS estates have no dependency map, no lineage record, and no reliable way to know what changed between the version that was built and the version that's actually deployed in the catalog.

What it needs.

This is a standalone Windows desktop application, not a PowerShell module — it doesn't need dbatools or PowerShell to run. It's built by the same author as the rest of this toolchain and is licensed separately: a full-featured 30-day trial, then either a machine-bound license or continued use with watermarked HTML exports.

Load a project, or a catalog.

1. Launch SsisAnalyzer.exeThe first run activates a 30-day full-featured trial automatically — no account, no registration.
2. Open with an empty workspaceAdd one or more sources from the File menu — see the table below.
3. Sources persistLoaded sources are remembered and reloaded automatically the next time you start the tool.

Loading projects

Loading from SSISDB: enter the server, choose Windows or SQL authentication, connect, then pick a folder and project from the catalog tree. The project binary is retrieved through catalog.get_project and parsed exactly like a file — catalog-specific metadata (deployment info, environments, parameter values, references) appears under the project's catalog branch. Passwords are never stored; SQL-authenticated sources ask for the password again the next time you reload.

Exploring a package

Expand a project in the tree: Project → Packages → Package. Every package shows:

The control-flow panel draws the package or container as boxes and dependency arrows, positioned from the saved layout; clicking a box selects the matching node in the tree. The search box (2+ characters) highlights and expands matches, Enter jumps to the next one, and the match count shows in the status bar. Execute SQL Tasks display their connection, parameter/result bindings, and the SQL itself — automatically formatted and syntax-highlighted.

See exactly what changed before you deploy it.

File → Compare projects… — pick project A (old) and B (new) from anything already loaded, in any mix of file and SSISDB sources. A common use: load the .ispac build output alongside the deployed SSISDB project, and compare before the deployment goes out.

Diff tree color coding

SQL changes are shown as a line-by-line diff. Two toggles cut the noise: Differences only, and Hide deployment-only (suppresses fields that only ever differ between a file and a deployed catalog copy, such as ProtectionLevel or the version GUID). Export as HTML… writes the comparison out as a standalone report.

What feeds what, across the whole workspace.

File → Lineage builds lineage across every loaded project at once — cross-project, end to end. Four tabs:

Column-level lineage is reliable within a single data flow, built from the SSIS lineageId. Table-level lineage sourced from Execute SQL Tasks is heuristic — it's parsed from the SQL text itself, not from a guaranteed metadata source. Export as HTML… from the lineage view produces a report that includes a drawn package-flow diagram.

Self-contained documentation, no server required.

File → Export HTML…, then choose a folder. This generates:

No external dependencies — open index.html in any browser, on any machine, with no server involved.

Named workspaces

File → Save workspace as… saves the current set of loaded sources to a .ssisws file; File → Open workspace… loads one back. Useful for keeping separate sets — DEV, PROD, a handover package — and the current workspace is also persisted automatically between sessions.

Scriptable for build pipelines and CI/CD.

The same engine that drives the GUI is available from the command line, for use in build processes and CI/CD pipelines.

SsisAnalyzer.exe --dump    <project.ispac>                  # Console summary of the parse
SsisAnalyzer.exe --export  <project.ispac> [outDir]         # Write the HTML documentation
SsisAnalyzer.exe --compare <a.ispac> <b.ispac> [out.html]   # Write a comparison report
SsisAnalyzer.exe --lineage <project.ispac>                  # Lineage summary + lineage.html

Try it fully, then license the machines that keep using it.

Why it's built this way.

Interface

A Visual Studio-style dark theme runs throughout — title bar, menus, toolbar, tree, tabs, and the control-flow diagram — with monochrome toolbar icons. The main window is a project/package tree on the left, the control-flow diagram top-right, and a read-only, syntax-highlighted details pane bottom-right.

Parsing

.ispac files and deployed SSISDB projects are read through the same parser, so a file and its deployed counterpart can be compared like-for-like. SSISDB access uses a single dependency, Microsoft.Data.SqlClient, and nothing else — no PowerShell, no dbatools, no external CLR requirement.

Security

Passwords for SQL-authenticated SSISDB sources are never written to disk; they're re-entered on each session that needs them. Licenses are RSA-signed and verified against an embedded public key — the private signing key never ships with the product.

Set up the catalog, then point SSIS Analyzer at it.

SSIS Analyzer reads an SSISDB catalog — it doesn't create one. These are the natural steps before and after using it.