MySQL data dictionary generator

Paste mysqldump --no-data output and get a data dictionary: every table, column, type, default, index and relationship as one printable document, with the inline COMMENT texts as descriptions. Parsed in your browser — the schema is never uploaded.

Your schema

CREATE TABLE `customers` (
  `id`         int unsigned NOT NULL AUTO_INCREMENT COMMENT 'Shown in the support portal URL',
  `email`      varchar(255) NOT NULL COMMENT 'Login identity',
  `plan`       varchar(20)  NOT NULL DEFAULT 'free',
  `created_at` timestamp    NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `uq_customers_email` (`email`)
) ENGINE=InnoDB COMMENT='Everyone who can open a ticket';

CREATE TABLE `agents` (
  `id`    int unsigned NOT NULL AUTO_INCREMENT,
  `name`  varchar(120) NOT NULL,
  `team`  varchar(60)  NOT NULL COMMENT 'billing / tech / escalations',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB COMMENT='Support staff';

CREATE TABLE `tickets` (
  `id`          int unsigned NOT NULL AUTO_INCREMENT COMMENT 'Ticket number, customer-visible',
  `customer_id` int unsigned NOT NULL,
  `subject`     varchar(200) NOT NULL,
  `status`      varchar(20)  NOT NULL DEFAULT 'open' COMMENT 'open -> pending -> solved -> closed',
  `opened_at`   timestamp    NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  KEY `idx_tickets_customer` (`customer_id`),
  CONSTRAINT `fk_tickets_customer` FOREIGN KEY (`customer_id`) REFERENCES `customers` (`id`)
) ENGINE=InnoDB COMMENT='Support requests; one row per conversation';

CREATE TABLE `messages` (
  `id`        bigint unsigned NOT NULL AUTO_INCREMENT,
  `ticket_id` int unsigned    NOT NULL COMMENT 'No FK on purpose: the app enforces it',
  `agent_id`  int unsigned    DEFAULT NULL COMMENT 'NULL when the customer wrote it',
  `body`      text            NOT NULL,
  `sent_at`   timestamp       NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  KEY `idx_messages_ticket` (`ticket_id`)
) ENGINE=InnoDB COMMENT='Every reply in every ticket';

CREATE TABLE `customers` (
  `id`         int unsigned NOT NULL AUTO_INCREMENT COMMENT 'Shown in the support portal URL',
  `email`      varchar(255) NOT NULL COMMENT 'Login identity',
  `plan`       varchar(20)  NOT NULL DEFAULT 'free',
  `created_at` timestamp    NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `uq_customers_email` (`email`)
) ENGINE=InnoDB COMMENT='Everyone who can open a ticket';

CREATE TABLE `agents` (
  `id`    int unsigned NOT NULL AUTO_INCREMENT,
  `name`  varchar(120) NOT NULL,
  `team`  varchar(60)  NOT NULL COMMENT 'billing / tech / escalations',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB COMMENT='Support staff';

CREATE TABLE `tickets` (
  `id`          int unsigned NOT NULL AUTO_INCREMENT COMMENT 'Ticket number, customer-visible',
  `customer_id` int unsigned NOT NULL,
  `subject`     varchar(200) NOT NULL,
  `status`      varchar(20)  NOT NULL DEFAULT 'open' COMMENT 'open -> pending -> solved -> closed',
  `opened_at`   timestamp    NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  KEY `idx_tickets_customer` (`customer_id`),
  CONSTRAINT `fk_tickets_customer` FOREIGN KEY (`customer_id`) REFERENCES `customers` (`id`)
) ENGINE=InnoDB COMMENT='Support requests; one row per conversation';

CREATE TABLE `messages` (
  `id`        bigint unsigned NOT NULL AUTO_INCREMENT,
  `ticket_id` int unsigned    NOT NULL COMMENT 'No FK on purpose: the app enforces it',
  `agent_id`  int unsigned    DEFAULT NULL COMMENT 'NULL when the customer wrote it',
  `body`      text            NOT NULL,
  `sent_at`   timestamp       NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  KEY `idx_messages_ticket` (`ticket_id`)
) ENGINE=InnoDB COMMENT='Every reply in every ticket';

Your diagram appears here.

The example is a MySQL support-desk schema; its COMMENT clauses fill the Description column. The messages table declares no foreign keys — watch its relations arrive dashed, matched by name.

From a MySQL server to a document

01mysqldump --no-data mydb > schema.sql — structure only, no rows. From Workbench: Server → Data Export → Dump Structure Only.
02Paste the file above or drop it onto the panel.
03Read the dictionary, then Save as PDF — the browser’s print dialog is the whole pipeline.

MySQL specifics the parser knows

Inline comments, both levels. COMMENT 'text' on columns and COMMENT='text' in table options become descriptions; quotes and '' escapes handled.
The dialect’s furniture. Backtick identifiers, unsigned, AUTO_INCREMENT, ENGINE= options, KEY /UNIQUE KEY index clauses — plus gaps in the standard grammar patched from real dumps (Dolibarr’s REAL columns, PrestaShop’s named inline primary keys).
Schemas without foreign keys. The MyISAM legacy: WordPress declares zero FKs across its whole schema. Relationships are inferred from column naming, drawn dashed, and counted separately — the dictionary never passes a guess off as a declared key.

FAQ

Is this the same thing as the MySQL 8 data dictionary?

No — MySQL 8 replaced its .frm files with an internal, transactional data dictionary that stores table metadata for the server itself. ErdDocs generates the other kind: a human-readable reference document of your schema for teammates, auditors and clients. The internal dictionary feeds the server; the one ErdDocs writes is the one you print, hand over and keep.

How do I export a MySQL schema for the dictionary?

mysqldump --no-data mydb > schema.sql dumps structure without rows; add --routines if you keep procedures. MySQL Workbench users: Server → Data Export → Dump Structure Only. Paste the result above — everything is parsed in the browser.

Where do the descriptions come from in MySQL?

MySQL keeps them inline: COMMENT 'text' after a column definition and COMMENT='text' among the table options. mysqldump preserves both, and they become the Description column of the dictionary. ALTER TABLE ... COMMENT works too — the comment lands in the next dump either way.

My MySQL dump declares no foreign keys. Will relationships be missing?

ErdDocs recovers them from column naming instead: a user_id column links to the users table, so the diagram still connects rather than falling apart into loose boxes. It is a common case — MyISAM never enforced foreign keys, and WordPress-style schemas declare none to this day. Recovered links are drawn dashed on the diagram and marked "matched by name" in the dictionary, so declared keys and inferred ones are never confused.

What does it cost?

Diagrams up to 25 tables and the dictionary preview are free, no account. One $9 payment unlocks the full dictionary and diagram for schemas of any size — once, not monthly.

Data dictionary generator — the dialect-neutral page.
PostgreSQL data dictionary generator — the same document from pg_dump.
SQL to ER diagram — the diagram side of the tool.