SQLParity

Schema Diff

Paste two CREATE TABLE statements, or two Elasticsearch index mappings. There is no format to pick — each side is read as whatever you paste into it.

1

Before

What you asked for.

2

After

What you actually got.

3

What differs

Paste a schema on both sides to see the difference.

How to Use Schema Diff

How to compare two database schemas and identify column discrepancies.

1

Paste Source DDL

Paste your baseline or source database CREATE TABLE statement into the first editor panel.

2

Paste Target DDL

Paste your updated or destination CREATE TABLE definition into the second editor panel.

3

Inspect Changes & Generate Checks

Review color-coded column additions (+), deletions (-), and type changes (~), then generate queries for only what changed.

Frequently Asked Questions

Common questions about privacy, supported dialects, and how Schema Diff works under the hood.

How does SQLParity detect column type changes?

The parser identifies type name aliases and precision changes (such as VARCHAR(50) to VARCHAR(255) or INT to BIGINT) and highlights type shifts that could cause data truncation.

Can I diff schemas from two different database engines?

Yes. You can paste a schema from SQL Server on the left and a schema from PostgreSQL or Snowflake on the right to compare equivalent column definitions across engines.

Is my proprietary schema uploaded or stored on any server?

No. The AST parser and diffing algorithm run purely in your browser tab. Your company table structures remain confidential.

Can I export the diff results for a pull request or code review?

Yes. You can copy the clean diff summary or copy validation queries directly into GitHub pull requests and Slack discussions.