ODBC SQL Parser for Java
General SQL Parser (GSP) parses ODBC with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage. One commercial SDK — ODBC is available in the Java edition.
ODBC SQL that GSP parses
SELECT {fn UCASE(customer_name)} AS customer_name
FROM customers
WHERE created_at >= {d '2026-01-01'};Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvodbc);
parser.sqltext = sql; // the ODBC 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 ODBC 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 ODBC
- {fn ...} scalar function escape sequences
- {d '...'}, {t '...'}, {ts '...'} date and time literal escapes
- {call ...} procedure invocation escapes
- {oj ...} outer join escapes
- Vendor-neutral ODBC specification SQL grammar
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for ODBC.
ODBC resources
- ODBC syntax reference — dialect documentation
- ODBC keyword compatibility — every keyword, and whether it can be an identifier
- ODBC capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
Common questions
Do I need a live ODBC database connection to validate SQL?
No. GSP validates ODBC 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 ODBC grammar?
GSP uses a dedicated hand-tuned grammar for ODBC — not a generic SQL grammar with flags. The parser recognizes 469 ODBC keywords and knows which 429 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the ODBC parser from C# / .NET?
Not currently. ODBC is a Java-edition dialect — the .NET library ships 15 dedicated grammars and ODBC 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 ODBC in .NET, email info@sqlparser.com; customer demand is how dialects get prioritized for the .NET port.
Can GSP extract column-level lineage from ODBC SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from ODBC scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.