SAP SQL Anywhere SQL Parser for Java

SAP SQL Anywhere SQL that GSP parses

CREATE PROCEDURE update_dept_count(IN dept INT)
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.dbvsqlanywhere);
parser.sqltext = sql; // the SAP SQL Anywhere 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 SQL Anywhere 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 SQL Anywhere

• LOAD TABLE bulk loading and UNLOAD-style OUTPUT
• Embedded SQL: ALLOCATE / GET / SET DESCRIPTOR, PREPARE, PUT
• CREATE EXISTING TABLE and FORWARD TO remote servers
• CREATE SERVICE web services and CREATE LOGIN POLICY
• Engine control: START/STOP DATABASE, START/STOP ENGINE, INSTALL JAVA
• Procedural SQL: Watcom-SQL and T-SQL procedure, function, and event definitions, with CALL, cursor blocks, and SIGNAL/RESIGNAL handlers

Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for SAP SQL Anywhere.

Recent SAP SQL Anywhere parser updates

• 2026-08-17 [SAP SQL Anywhere] Dedicated vendor with its own grammar, statement splitter, and syntax coverage page
• 2026-08-17 [SAP SQL Anywhere] Reject Sybase IQ specialized index types and IQ-only DDL
• 2026-08-17 [SAP SQL Anywhere] Reject ASE-only statements such as DUMP TRANSACTION and READTEXT, naming the product each belongs to

Full history in the release notes.