SQL SURGEONv1.2
100% LOCAL PROCESSINGHow it works
THE SCHEMA COMPARISON OPERATING ROOM

Compare with confidence.
Deploy without surprises.

Two schema dumps in. A clear migration plan out. No database connections, no accounts, and absolutely no SQL sent to a server.

01 / UPLOAD

Choose your schemas

Upload schema-only .sql exports. Production is never touched.

SCHEMA EXPORT MADE SIMPLE

Don't have your schema files?

Get a clean, structure-only export from DEV and PROD. No data rows, no database connection to our site.

01 · DESIRED SCHEMANO FILE

Source · DEV

Drop the schema you want to end up with

COMPARE
02 · CURRENT SCHEMANO FILE

Target · PROD

Drop the schema that currently exists

Private by designYour SQL stays in this browser tab. File contents are never uploaded or stored by this app.
THE FINE PRINT

Precision over guesswork.

01

MySQL & MariaDB

Built for schema-only CREATE TABLE exports, including common phpMyAdmin ALTER TABLE definitions. Unsupported DDL is reported, never silently interpreted as safe.

02

No SQL collection

No backend, analytics, third-party scripts, cookies or network requests for file contents. Source and target are held only in tab memory.

03

Human in control

Risky alterations are off by default. Review the generated SQL before you execute it against any database.

EXPORT ASSISTANT PRIVATE BY DESIGN

Your schema, ready in minutes.

Export just the database structure. Everything happens on your machine.

01Choose database02Export structure03Import & compare
Which database are you exporting?
No passwords or connections

Export only the structure with phpMyAdmin

  1. Log into your own phpMyAdmin and select the DEV database in the sidebar (not the server).
  2. Choose Export → Custom. Set the format to SQL.
  3. Under the table export options, select Structure and deselect Data. Include all tables; omit triggers, routines, events and views where those options are available.
  4. Disable DROP TABLE statements if the interface offers that setting. Click Export / Go and save the .sql file on your computer.
  5. Come back and upload the file in the Source · DEV panel. Repeat for the other database.
Check before import: the file should contain CREATE TABLE definitions, not INSERT INTO records. Schema defaults, names and comments can still be sensitive.