How to use SQL Schema Change Analyzer
- Paste the before and after CREATE TABLE declarations.
- Confirm the PostgreSQL-like subset matches the supplied syntax.
- Review column removals, type changes, nullability and key changes.
- Export the findings and prepare any migration separately under database review.
Example: SQL Schema Change Analyzer
Compare supported CREATE TABLE columns, keys and constraints.
Supported inputs and limits
- Each DDL input is limited to 100,000 UTF-8 bytes, 12 tables, 120 total columns, 12,000 tokens and 40 foreign keys.
- Only the existing PostgreSQL-like CREATE TABLE parser subset is accepted.
- Supports named columns, documented plain types and primary, unique or foreign keys.
- Defaults, CHECK, named constraints, indexes, generated expressions, ALTER and MySQL/MariaDB options are refused.
- No database is contacted and no executable migration is produced.
More details
Type and key changes require review rather than automatic safety classification.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Questions about SQL Schema Change Analyzer
Can I compare a MariaDB schema dump?
Only statements that fit the declared PostgreSQL-like subset are supported. MariaDB dialect options, backticks, engine clauses and other unparsed syntax are refused.
Does a type change always count as breaking?
A type change is marked for review. Actual compatibility depends on the database, values, conversion rules and clients, which this local structural comparison does not execute.
Will the tool create or apply ALTER statements?
It exports a change report. Migration generation and execution are deliberately outside this tool, so a report cannot change your database.