SQL dialect
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, 38 dialects, Java and .NET.
Example
IBM Netezza SQL that GSP parses
GROOM TABLE sales RECORDS ALL;
GENERATE STATISTICS ON sales;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());
}The .NET edition exposes the same API in C# — see the C# quick start.
Coverage
What GSP handles in IBM Netezza
- GROOM TABLE
- GENERATE STATISTICS
- External tables
- CALL/EXECUTE PROCEDURE
- LIMIT with offset
- Procedural SQL: NZPLSQL stored procedures, including CREATE PROCEDURE and CALL/EXECUTE PROCEDURE invocation
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for IBM Netezza.
Actively maintained
Recent IBM Netezza parser updates
- 2026-03-15 [Netezza] Fix AexprConst precedence and trim whitespace
- 2026-02-17 Add Netezza TIMESTAMP(date, time) function support
- 2026-01-16 Add Netezza CALL/EXECUTE PROCEDURE syntax support
Full history in the release notes.
Go deeper
IBM Netezza resources
- IBM Netezza syntax reference — dialect documentation
- IBM Netezza 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 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 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 392 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 (NuGet package gudusoft.gsqlparser, .NET Standard 2.0) exposes the same API surface as the Java edition, so every IBM Netezza parsing feature on this page works in C# and VB.NET.
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.