IBM Netezza SQL Parser for Java and .NET

General SQL Parser (GSP) parses IBM Netezza 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.

89%
of 73 documented IBM Netezza constructs parse fully — measured on GSP 4.2.6 (2026-08-18)
435
IBM Netezza keywords recognized by the grammar
432
keywords the parser also accepts as identifiers
127
IBM Netezza test SQL files in the regression corpus
Weekly
release cadence — dialect fixes ship in days

IBM Netezza SQL that GSP parses

GROOM TABLE sales RECORDS ALL;
GENERATE STATISTICS ON sales;

Need us to check your own IBM Netezza SQL? Send a sample.

Parse it in Java

import gudusoft.gsqlparser.*;

TGSqlParser parser = new TGSqlParser(EDbVendor.dbvnetezza);
parser.sqltext = sql; // the IBM Netezza 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.dbvnetezza);
parser.sqltext = sql; // the IBM Netezza 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 Netezza

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

Recent IBM Netezza parser updates

Full history in the release notes.

IBM Netezza resources

Common questions

Does GSP parse IBM Netezza stored procedures and procedural SQL?

Yes. GSP parses NZPLSQL stored procedures, including CREATE PROCEDURE and CALL/EXECUTE PROCEDURE invocation 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 Netezza database connection to validate SQL?

No. GSP validates IBM Netezza 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 Netezza grammar?

GSP uses a dedicated hand-tuned grammar for IBM Netezza — not a generic SQL grammar with flags. The parser recognizes 435 IBM Netezza keywords and knows which 432 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 Netezza parser from C# / .NET?

Yes. The .NET edition parses IBM Netezza 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 Netezza SQL?

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