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, available for Java and .NET.

66%
of 47 documented Teradata constructs parse fully — measured on GSP 4.1.9 (2026-08-01)
702
Teradata keywords recognized by the grammar
698
keywords the parser also accepts as identifiers
605
Teradata test SQL files in the regression corpus
Weekly
release cadence — dialect fixes ship in days

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());
}

Parse it in C#

using gudusoft.gsqlparser;

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

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

Recent Teradata parser updates

Full history in the release notes.

Teradata resources

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 live 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 698 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 parses Teradata 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 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.