ERD diagram from SQL Server SQL
You do not pick the dialect from a list — it shows in the script itself. Here is what the editor finds in a typical SQL Server schema.
The inputschema.sql
CREATE TABLE users (
id BIGINT IDENTITY(1,1) PRIMARY KEY,
email NVARCHAR(255) NOT NULL UNIQUE,
full_name NVARCHAR(120),
is_active BIT NOT NULL,
created_at DATETIME2 NOT NULL
);
CREATE TABLE orders (
id BIGINT IDENTITY(1,1) PRIMARY KEY,
user_id BIGINT NOT NULL REFERENCES users(id),
total DECIMAL(12,2) NOT NULL,
note NVARCHAR(MAX),
placed_at DATETIME2 NOT NULL
);- Detected as
SQL Server- Told apart by
IDENTITY(1,1) · DATETIME2 · (MAX) · NVARCHAR · BIT
Parsed: 2 tables, 1 relation
Open the editor
The script stays in the browser: both parsing and generation run on your machine, nothing goes to a server.
Types of this dialect the editor knows
INTBIGINTSMALLINTTINYINTBITDECIMAL(12,2)FLOATMONEYNVARCHAR(255)VARCHAR(255)NCHAR(2)DATEDATETIME2DATETIMEOFFSETTIMEUNIQUEIDENTIFIERVARBINARY(MAX)