SQL parser solutions for migration and metadata
GSP gives Java and .NET teams a dialect-aware AST, dependency extraction, validation, rewriting, and lineage foundation. These guides show where that foundation fits into a concrete migration or metadata workflow—and where a parser stops short of doing the whole job.
Migration and modernization
A migration starts with evidence: which files parse, which dialect constructs appear, which objects depend on each other, and which transformations can be automated safely. Published guides contain measured coverage and concrete Java/.NET paths. Planned guides are listed early so teams can submit representative scripts before publication.
- Sybase T-SQLPublished
Build a Java or .NET inventory of Sybase ASE and IQ scripts, stored procedures, dependencies, and syntax that needs deliberate migration work.
- Oracle PL/SQLPlanned
Inventory packages, procedures, triggers, dynamic SQL, and object dependencies before an Oracle modernization project begins.
- Informix SPLPlanned
Classify Informix SPL routines and extract the tables, columns, calls, and dialect-specific constructs that affect modernization scope.
- IBM Db2 SQL PLPlanned
Analyze Db2 SQL PL routines, compound statements, object references, and compatibility work before changing platforms.
- Teradata BTEQPlanned
Separate BTEQ control flow from Teradata SQL and map the dependencies that a warehouse migration must preserve.
- IBM NetezzaPlanned
Inventory Netezza SQL, procedural objects, and warehouse dependencies before moving workloads to a new analytical platform.
Catalog and lineage integrations
GSP also supplies the SQL parsing and column-level lineage layer for metadata platforms. These integration guides cover deployment, ingestion boundaries, diagnostics, and verification.
- DataHubPublished
Parse SQL sources and publish table- and column-level lineage into DataHub.
- OpenMetadataPublished
Run GSP as an offline lineage sidecar and return OpenMetadata-compatible relationships.
Start with one difficult script
Send a stored procedure, migration script, or dynamic SQL block with customer data removed. Gudu will check the syntax shape and identify the appropriate parser, AST, validation, or lineage path before you commit to a larger evaluation.