Sybase SQL Parser for Java and .NET
General SQL Parser (GSP) parses Sybase 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.
Sybase SQL that GSP parses
CREATE PROCEDURE update_dept_count @dept INT AS
BEGIN
UPDATE dept SET cnt = (SELECT COUNT(*) FROM emp WHERE emp.dept_id = @dept)
WHERE dept.id = @dept
END Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvsybase);
parser.sqltext = sql; // the Sybase 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.dbvsybase);
parser.sqltext = sql; // the Sybase 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 Sybase
- Stored procedures (T-SQL)
- Watcom IF...THEN...END IF
- WRITETEXT and INSERT BULK
- DUMP TRANSACTION
- ON COMMIT ROWS
- Procedural SQL: Transact-SQL stored procedures and functions with exception handlers, including Sybase IQ procedure bodies and Watcom IF...THEN...END IF
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Sybase.
Planning a Sybase modernization project? See how to build a Sybase T-SQL migration inventory in Java or .NET without treating the parser as an end-to-end code converter.
Recent Sybase parser updates
- 2026-07-06 [Sybase] Support empty statements and ON COMMIT ROWS
- 2026-05-29 [Sybase] Support Watcom IF ... THEN ... END IF in procedure bodies
- 2026-05-19 [Sybase] Hook EXCEPTION clause into TBlockSqlNode + TMssqlBlock
Full history in the release notes.
Sybase resources
- Sybase syntax reference — dialect documentation
- Sybase keyword compatibility — every keyword, and whether it can be an identifier
- Sybase capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — .NET setup and first parse
Common questions
Does GSP parse Sybase stored procedures and procedural SQL?
Yes. GSP parses Transact-SQL stored procedures and functions with exception handlers, including Sybase IQ procedure bodies and Watcom IF...THEN...END IF 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 Sybase database connection to validate SQL?
No. GSP validates Sybase 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 Sybase grammar?
GSP uses a dedicated hand-tuned grammar for Sybase — not a generic SQL grammar with flags. The parser recognizes 456 Sybase keywords and knows which 413 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Sybase parser from C# / .NET?
Yes. The .NET edition parses Sybase 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 Sybase SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Sybase scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.