IBM Db2 SQL Parser for Java and .NET

General SQL Parser (GSP) parses IBM Db2 with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage, including complete procedural SQL support. One commercial SDK, available for Java and .NET.

61%
of 174 documented IBM Db2 constructs parse fully — measured on GSP 4.1.9 (2026-08-01)
573
IBM Db2 keywords recognized by the grammar
570
keywords the parser also accepts as identifiers
265
IBM Db2 test SQL files in the regression corpus
Weekly
release cadence — dialect fixes ship in days

IBM Db2 SQL that GSP parses

CREATE PROCEDURE update_salary(IN p_id INT)
BEGIN
  DECLARE v_count INT DEFAULT 0;
  UPDATE staff SET salary = salary * 1.05 WHERE id = p_id;
END

Parse it in Java

import gudusoft.gsqlparser.*;

TGSqlParser parser = new TGSqlParser(EDbVendor.dbvdb2);
parser.sqltext = sql; // the IBM Db2 SQL above
if (parser.parse() == 0) {
    System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
    System.out.println(parser.getErrormessage());
}

Parse it in C#

using gudusoft.gsqlparser;

TGSqlParser parser = new TGSqlParser(EDbVendor.dbvdb2);
parser.sqltext = sql; // the IBM Db2 SQL above
if (parser.parse() == 0)
{
    Console.WriteLine(parser.sqlstatements.size() + " statement(s) parsed");
}
else
{
    Console.WriteLine(parser.Errormessage);
}

Same grammar, .NET-idiomatic API — properties instead of Java getters. See the C# quick start or the .NET SQL Parser SDK.

What GSP handles in IBM Db2

Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for IBM Db2.

Recent IBM Db2 parser updates

Full history in the release notes.

IBM Db2 resources

Common questions

Does GSP parse IBM Db2 stored procedures and procedural SQL?

Yes. GSP parses SQL PL procedures, functions, and triggers with cursors, condition handlers, and dynamic compound statements into a full AST — procedure bodies become real statement trees you can traverse, not opaque text blocks. This is what makes lineage and impact analysis work inside procedural code.

Do I need a live IBM Db2 database connection to validate SQL?

No. GSP validates IBM Db2 syntax completely offline. You get error line and column positions, the offending token, and a hint — with no server, driver, or credentials involved.

How complete is the IBM Db2 grammar?

GSP uses a dedicated hand-tuned grammar for IBM Db2 — not a generic SQL grammar with flags. The parser recognizes 573 IBM Db2 keywords and knows which 570 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.

Can I use the IBM Db2 parser from C# / .NET?

Yes. The .NET edition parses IBM Db2 with the same grammar, and the API is idiomatic .NET rather than a Java transliteration: where Java has parser.getErrormessage() and stmt.getResultColumnList(), C# has parser.Errormessage and stmt.ResultColumnList. The package id is gudusoft.gsqlparser, multi-targeting net10.0 and netstandard2.0, so .NET Framework 4.6.2+ hosts are covered too.

Can GSP extract column-level lineage from IBM Db2 SQL?

Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from IBM Db2 scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.