SQL parser evaluation

Send a SQL sample for parser review

Have a stored procedure, migration script, dynamic SQL block, or AI-generated query that is hard to parse? Share a representative sample and we will review compatibility, dialect risks, expected outputs, and evaluation options.

Parser compatibilityDoes the SQL fit the right GSP dialect path?
Dialect risk reviewWhich syntax may need special handling?
Output guidanceAST, tables, columns, lineage, validation, or risk checks.

Evaluation request

Describe your SQL and expected output

This public form opens your email client with a structured message to Gudu Software. If your SQL is large, paste a short representative sample here and mention that you can send a file attachment by email.

Please remove private connection details, login values, production PII, and confidential customer data before sharing SQL.

If the button does not open your email client, copy the template below and send it to info@sqlparser.com.

Technical evaluation scope

Useful review outputs for enterprise parser evaluation

Parse-rate directionHow the sample maps to supported dialect parsing and where edge cases may appear.
Unsupported syntax reportSyntax patterns that may require configuration, preprocessing, or support review.
Lineage output sampleWhether the sample is suitable for table-level or column-level lineage evaluation.
Integration recommendationSuggested Java SDK workflow, trial package, support path, or license discussion.

Copy/paste template

Name:
Work email:
Company:
Use case: parser / lineage / validation / migration / AI SQL guard / other
Database dialect:
Target runtime: Java / .NET / REST / not sure
Expected output: AST / tables / columns / lineage / validation errors / risk checks
Timeline: research / active POC / purchasing / renewal

SQL sample, with sensitive data removed:

What should GSP return?