Snowflake SQL Parser for Java and .NET

General SQL Parser (GSP) parses Snowflake 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.

79%
of 455 documented Snowflake constructs parse fully — measured on GSP 4.1.9 (2026-07-30)
730
Snowflake keywords recognized by the grammar
689
keywords the parser also accepts as identifiers
1,331
Snowflake test SQL files in the regression corpus
Weekly
release cadence — dialect fixes ship in days

Snowflake SQL that GSP parses

COPY INTO mytable
FROM @my_int_stage
FILE_FORMAT = (TYPE = CSV);

Parse it in Java

import gudusoft.gsqlparser.*;

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

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

Recent Snowflake parser updates

Full history in the release notes.

Snowflake resources

Common questions

Does GSP parse Snowflake stored procedures and procedural SQL?

Yes. GSP parses SQL stored procedures and standalone Snowflake Scripting blocks, including COPY INTO inside procedure bodies 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 Snowflake database connection to validate SQL?

No. GSP validates Snowflake 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 Snowflake grammar?

GSP uses a dedicated hand-tuned grammar for Snowflake — not a generic SQL grammar with flags. The parser recognizes 730 Snowflake keywords and knows which 689 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.

Can I use the Snowflake parser from C# / .NET?

Yes. The .NET edition parses Snowflake 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 Snowflake SQL?

Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Snowflake scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.