SAP HANA SQL Parser for Java
General SQL Parser (GSP) parses SAP HANA 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 — SAP HANA is available in the Java edition.
SAP HANA SQL that GSP parses
CREATE PROCEDURE top_customers(OUT result INT)
LANGUAGE SQLSCRIPT AS
BEGIN
SELECT COUNT(*) INTO result FROM customers;
ENDParse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvhana);
parser.sqltext = sql; // the SAP HANA SQL above
if (parser.parse() == 0) {
System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
System.out.println(parser.getErrormessage());
}Java edition only. The .NET library has no SAP HANA grammar, so this dialect cannot be parsed from C# or VB.NET. See the .NET SQL Parser SDK for the dialects it does cover.
What GSP handles in SAP HANA
- SQLScript procedures
- Fulltext indexes
- Graph workspaces
- Virtual tables and remote sources
- WITH RANGE_RESTRICTION
- Procedural SQL: SQLScript procedures and functions (CREATE/ALTER PROCEDURE), block statements, and virtual procedures
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for SAP HANA.
Recent SAP HANA parser updates
- 2026-05-25 [Hana] Support WITH RANGE_RESTRICTION clause
- 2026-01-14 Add SAP HANA block statement support (MantisBT #4285)
- 2026-01-10 Fix HANA REVOKE statement splitting issue
Full history in the release notes.
SAP HANA resources
- SAP HANA syntax reference — dialect documentation
- SAP HANA keyword compatibility — every keyword, and whether it can be an identifier
- SAP HANA capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
Common questions
Does GSP parse SAP HANA stored procedures and procedural SQL?
Yes. GSP parses SQLScript procedures and functions (CREATE/ALTER PROCEDURE), block statements, and virtual 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 live SAP HANA database connection to validate SQL?
No. GSP validates SAP HANA 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 SAP HANA grammar?
GSP uses a dedicated hand-tuned grammar for SAP HANA — not a generic SQL grammar with flags. The parser recognizes 655 SAP HANA keywords and knows which 643 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the SAP HANA parser from C# / .NET?
Not currently. SAP HANA is a Java-edition dialect — the .NET library ships 15 dedicated grammars and SAP HANA is not one of them, so there is no C# code path for it. Everything else on this page describes the Java SDK. If you need SAP HANA in .NET, email info@sqlparser.com; customer demand is how dialects get prioritized for the .NET port.
Can GSP extract column-level lineage from SAP HANA SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from SAP HANA scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.