SQL dialect
Vertica SQL Parser for Java and .NET
General SQL Parser (GSP) parses Vertica with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage . One commercial SDK, 38 dialects, Java and .NET.
Example
Vertica SQL that GSP parses
CREATE PROJECTION sales_proj AS
SELECT id, region, amt FROM sales
ORDER BY region
SEGMENTED BY HASH(id) ALL NODES; Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvvertica);
parser.sqltext = sql; // the Vertica 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 Vertica
- CREATE PROJECTION ... AS SELECT
- Flex tables
- Access policies
- Resource pools
- EXPORT TO VERTICA
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Vertica.
Actively maintained
Recent Vertica parser updates
- 2026-06-02 [Vertica] Parse AUTO_INCREMENT column attribute
- 2026-05-08 [Vertica] Support AND filter and WHERE in MERGE clauses
- 2026-04-05 [Vertica] Parse AS SELECT subquery in CREATE PROJECTION
Full history in the release notes.
Go deeper
Vertica resources
- Vertica syntax reference — dialect documentation
- Vertica 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
Do I need a Vertica database connection to validate SQL?
No. GSP validates Vertica 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 Vertica grammar?
GSP uses a dedicated hand-tuned grammar for Vertica — not a generic SQL grammar with flags. The parser recognizes 576 Vertica keywords and knows which 512 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Vertica 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 Vertica parsing feature on this page works in C# and VB.NET.
Can GSP extract column-level lineage from Vertica SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Vertica scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.