SQL dialect
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, 38 dialects, Java and .NET.
Example
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());
}The .NET edition exposes the same API in C# — see the C# quick start.
Coverage
What GSP handles in Snowflake
- COPY INTO (stages)
- Snowflake Scripting blocks
- Tasks, streams, and pipes
- Dynamic tables
- Semi-structured colon paths
- Procedural SQL: SQL stored procedures and standalone Snowflake Scripting blocks, including COPY INTO inside procedure bodies
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Snowflake.
Actively maintained
Recent Snowflake parser updates
- 2026-07-02 [Snowflake] Support GRANT OWNERSHIP COPY CURRENT GRANTS
- 2026-06-18 [Snowflake] Support SCOPED TEMPORARY table
- 2026-06-18 [Snowflake] Allow colon path access on constants
Full history in the release notes.
Go deeper
Snowflake resources
- Snowflake syntax reference — dialect documentation
- Snowflake 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 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 (NuGet package gudusoft.gsqlparser, .NET Standard 2.0) exposes the same API surface as the Java edition, so every Snowflake parsing feature on this page works in C# and VB.NET.
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.