Sybase ASE SQL Parser for Java
General SQL Parser (GSP) parses Sybase ASE with a dedicated Adaptive Server Enterprise grammar (separate from the permissive Sybase vendor that spans the whole family) — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage, including complete procedural SQL support. One commercial SDK — Sybase ASE is available in the Java edition.
Sybase ASE 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.dbvsybasease);
parser.sqltext = sql; // the Sybase ASE 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 Sybase ASE 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 Sybase ASE
- T-SQL procedures, triggers, and CREATE OR REPLACE PROCEDURE
- DUMP TRANSACTION, DBCC, and UPDATE/DELETE STATISTICS
- CREATE EXISTING TABLE (Component Integration Services)
- Global variables (@@identity) and COMPUTE clauses
- SET IDENTITY_INSERT, SETUSER, LOCK TABLE
- Procedural SQL: Transact-SQL stored procedures, triggers, and user-defined functions, including CREATE OR REPLACE PROCEDURE and DECLARE CURSOR blocks
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Sybase ASE.
Recent Sybase ASE parser updates
- 2026-08-17 [Sybase ASE] Dedicated ASE vendor with its own grammar, statement splitter, and syntax coverage page
- 2026-08-17 [Sybase ASE] Reject Watcom-SQL procedure syntax that belongs to SQL Anywhere
- 2026-08-17 [Sybase ASE] Reject Sybase IQ specialized index types and IQ-only DDL
Full history in the release notes.
Sybase ASE resources
- Sybase ASE syntax reference — dialect documentation
- Sybase ASE 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 Sybase ASE stored procedures and procedural SQL?
Yes. GSP parses Transact-SQL stored procedures, triggers, and user-defined functions, including CREATE OR REPLACE PROCEDURE and DECLARE CURSOR blocks 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 ASE database connection to validate SQL?
No. GSP validates Sybase ASE syntax completely offline. You get error line and column positions, the offending token, and a hint — with no server, driver, or credentials involved.
Can I use the Sybase ASE parser from C# / .NET?
Not currently. Sybase ASE is a Java-edition dialect — the .NET library ships 15 dedicated grammars and Sybase ASE 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 Sybase ASE in .NET, email info@sqlparser.com; customer demand is how dialects get prioritized for the .NET port.
Can GSP extract column-level lineage from Sybase ASE SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Sybase ASE scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.