SQL dialect
Teradata SQL Parser for Java and .NET
General SQL Parser (GSP) parses Teradata 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
Teradata SQL that GSP parses
SELECT store_id, sales_amt,
RANK() OVER (PARTITION BY store_id ORDER BY sales_amt DESC) AS rnk
FROM daily_sales
QUALIFY rnk <= 3;Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvteradata);
parser.sqltext = sql; // the Teradata 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 Teradata
- QUALIFY clause
- BTEQ scripts
- FastLoad/MultiLoad/FastExport
- COLLECT STATISTICS
- Period predicates (MEETS/PRECEDES)
- Procedural SQL: Stored procedures and triggers plus BTEQ scripts, including FastLoad, MultiLoad, and FastExport utility commands
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Teradata.
Actively maintained
Recent Teradata parser updates
- 2026-06-18 [Teradata] Parse MEETS/PRECEDES/SUCCEEDS period predicates
- 2026-06-05 [Teradata] Support PIVOT DEFAULT ON NULL clause
- 2026-05-25 [Teradata] Allow optional alias in MERGE USING VALUES
Full history in the release notes.
Go deeper
Teradata resources
- Teradata syntax reference — dialect documentation
- Teradata 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 Teradata stored procedures and procedural SQL?
Yes. GSP parses Stored procedures and triggers plus BTEQ scripts, including FastLoad, MultiLoad, and FastExport utility commands 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 Teradata database connection to validate SQL?
No. GSP validates Teradata 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 Teradata grammar?
GSP uses a dedicated hand-tuned grammar for Teradata — not a generic SQL grammar with flags. The parser recognizes 702 Teradata keywords and knows which 652 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Teradata 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 Teradata parsing feature on this page works in C# and VB.NET.
Can GSP extract column-level lineage from Teradata SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Teradata scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.