SQL dialect
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, 38 dialects, Java and .NET.
Example
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;
ENDParse 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());
}The .NET edition exposes the same API in C# — see the C# quick start.
Coverage
What GSP handles in IBM Db2
- SQL PL compound statements
- Condition handlers
- Cursor declarations
- FETCH FIRST n ROWS
- IMPLICITLY HIDDEN columns
- Procedural SQL: SQL PL procedures, functions, and triggers with cursors, condition handlers, and dynamic compound statements
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for IBM Db2.
Actively maintained
Recent IBM Db2 parser updates
- 2026-06-02 [DB2] Surface stored-procedure CALL in dlineage call graph
- 2026-06-02 [DB2] Populate FETCH FIRST n count on TFetchFirstClause
- 2026-04-18 [DB2] Support IMPLICITLY HIDDEN column attribute
Full history in the release notes.
Go deeper
IBM Db2 resources
- IBM Db2 syntax reference — dialect documentation
- IBM Db2 keyword compatibility — every keyword, and whether it can be an identifier
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — NuGet setup for .NET
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 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 547 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 (NuGet package gudusoft.gsqlparser, .NET Standard 2.0) exposes the same API surface as the Java edition, so every IBM Db2 parsing feature on this page works in C# and VB.NET.
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.