SQL dialect
Amazon Redshift SQL Parser for Java and .NET
General SQL Parser (GSP) parses Amazon Redshift 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
Amazon Redshift SQL that GSP parses
COPY sales
FROM 's3://mybucket/data/'
IAM_ROLE 'arn:aws:iam::0123456789:role/MyRole'
FORMAT AS PARQUET;Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvredshift);
parser.sqltext = sql; // the Amazon Redshift 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 Amazon Redshift
- COPY and UNLOAD
- SUPER semi-structured UNPIVOT
- $$-quoted UDF bodies
- Stored procedures
- LIKE/ILIKE ... ESCAPE
- Procedural SQL: PL/pgSQL-style stored procedures with $$-quoted bodies, including NONATOMIC procedures
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Amazon Redshift.
Actively maintained
Recent Amazon Redshift parser updates
- 2026-07-08 [Redshift] Support SUPER object UNPIVOT in FROM clause
- 2026-07-08 [Redshift] Support $$-quoted SQL UDF body with semicolons
- 2026-07-08 [Redshift] Support UNLOAD EXTENSION AS clause
Full history in the release notes.
Go deeper
Amazon Redshift resources
- Amazon Redshift syntax reference — dialect documentation
- Amazon Redshift 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 Amazon Redshift stored procedures and procedural SQL?
Yes. GSP parses PL/pgSQL-style stored procedures with $$-quoted bodies, including NONATOMIC procedures 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 Amazon Redshift database connection to validate SQL?
No. GSP validates Amazon Redshift 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 Amazon Redshift grammar?
GSP uses a dedicated hand-tuned grammar for Amazon Redshift — not a generic SQL grammar with flags. The parser recognizes 488 Amazon Redshift keywords and knows which 463 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Amazon Redshift 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 Amazon Redshift parsing feature on this page works in C# and VB.NET.
Can GSP extract column-level lineage from Amazon Redshift SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Amazon Redshift scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.