You already have your schema as SQL. Drawing it again by hand, box by box, is the part nobody enjoys. Here is a way to skip it: paste the CREATE TABLE statements and let the diagram draw itself.
I'm the maker of Systemap, a diagram editor that runs in the browser. This post walks through its SQL import. You can follow along without an account.
The schema
A small issue tracker: users, projects, issues and comments.
CREATE TABLE users ( id uuid PRIMARY KEY, name text NOT NULL, email text NOT NULL UNIQUE ); CREATE TABLE projects ( id uuid PRIMARY KEY, name text NOT NULL ); CREATE TABLE issues ( id bigserial PRIMARY KEY, project_id uuid NOT NULL REFERENCES projects(id), assignee_id uuid REFERENCES users(id), title text NOT NULL ); CREATE TABLE comments ( id bigserial PRIMARY KEY, issue_id bigint NOT NULL REFERENCES issues(id), author_id uuid NOT NULL, body text NOT NULL ); Look at comments.author_id. It points at a user, but nobody wrote the REFERENCES. We'll fix that in the diagram.
Steps
Step 1. Open www.systemap.app and click Try it now. No sign-up.
Step 2. In the Page panel on the right, under Create, click Import SQL.
Step 3. Paste the statements and click Replace page with this schema, then Close.
Each table becomes a box with its columns. Each REFERENCES becomes a 1:N relationship line. With the schema above you get four tables and three lines.
One thing to know: import replaces what is on the page. Start on a new page if you want to keep a drawing.
The foreign key your SQL forgot
comments.author_id has no line, because the SQL never declared one.
Double-click the comments table, start typing in the References field of author_id, and pick users.id from the list. The primary keys on the page come first. The line draws itself.
What you can do with it
Save the diagram as a PNG for a design doc or a pull request. That works without an account. Sharing a link or exporting a video needs a free account.
The 40-second video version of this walkthrough: https://youtu.be/D763_Yt2GLI
If your schema imports wrong, tell me in the comments which statement broke. The import targets PostgreSQL syntax today.