Convert a SQLite schema to SQL Server
Paste the CREATE TABLE statements from SQLite and ERD Designer draws them as a diagram. Change the diagram's target database to SQL Server and every column's datatype is converted. You review each change before it is applied, then generate the SQL Server script.
What changes in the sample
Converted to SQL Server 2022, these columns of the sample above change type. Everything else keeps its type; names, keys, nullability and lists of allowed values are left as they are.
| Column | SQLite | SQL Server | Note |
|---|---|---|---|
customers.customer_id | INTEGER identity | BIGINT | numbered by the database |
customers.email | TEXT | NVARCHAR(255) | |
customers.full_name | VARCHAR(120) | NVARCHAR(120) | |
customers.notes | TEXT | NVARCHAR(MAX) | |
customers.is_active | BOOLEAN | BIT | |
customers.created_at | DATETIME | DATETIME2 | |
orders.order_id | INTEGER identity | BIGINT | numbered by the database |
orders.customer_id | INTEGER | BIGINT | |
orders.status | TEXT | NVARCHAR(7) | |
orders.placed_at | DATETIME | DATETIME2 | |
orders.receipt_pdf | BLOB | VARBINARY(MAX) |
What it tells you
Where a conversion loses something, ERD Designer says so rather than picking for you. These are the messages for the sample:
- customers.email: SQL Server cannot use NVARCHAR(MAX) as a key or index it — converted to NVARCHAR(255); widen it if your values are longer.
The SQL Server script
This is what ERD Designer generates for the sample, for SQL Server 2022. Our test suite applies this conversion to a real SQL Server server and then reads the database back to confirm it matches the diagram exactly.
-- Create table customers
CREATE TABLE [customers] (
[customer_id] BIGINT IDENTITY(1,1) NOT NULL,
[email] NVARCHAR(255) NOT NULL,
[full_name] NVARCHAR(120) NOT NULL,
[notes] NVARCHAR(MAX) NULL,
[is_active] BIT NOT NULL CONSTRAINT [DF_customers_is_active] DEFAULT (1),
[created_at] DATETIME2(7) NOT NULL CONSTRAINT [DF_customers_created_at] DEFAULT (CURRENT_TIMESTAMP),
CONSTRAINT [customers_PK] PRIMARY KEY ([customer_id])
);
-- Create table orders
CREATE TABLE [orders] (
[order_id] BIGINT IDENTITY(1,1) NOT NULL,
[customer_id] BIGINT NOT NULL,
[status] NVARCHAR(7) NOT NULL CONSTRAINT [DF_orders_status] DEFAULT (N'new') CHECK ([status] IN (N'new', N'paid', N'shipped')),
[total] NUMERIC(12,2) NOT NULL,
[placed_at] DATETIME2(7) NOT NULL,
[receipt_pdf] VARBINARY(MAX) NULL,
CONSTRAINT [orders_PK] PRIMARY KEY ([order_id])
);
-- Add unique constraint on customers (email)
ALTER TABLE [customers] ADD CONSTRAINT [customers_UQ1] UNIQUE ([email]);
-- Create index on orders (placed_at)
CREATE INDEX [orders_placed_ix] ON [orders] ([placed_at]);
-- Add foreign key orders (customer_id) → customers (customer_id)
ALTER TABLE [orders] ADD CONSTRAINT [orders_FK1] FOREIGN KEY ([customer_id]) REFERENCES [customers] ([customer_id]);
How to convert your own schema
- Paste your SQLite script above and press Open in ERD Designer. The diagram opens laid out and ready to edit.
- Click the diagram's name in the toolbar to open its properties, choose SQL Server under Target Database / Version, and press Apply Changes.
- If SQL Server offers more than one way to store a kind of column, choose one and press Continue.
- Read the list of retyped columns and any warnings, then press Apply Conversion. Save the diagram to keep it.
- Press Generate DDL (the database icon) to copy or download the SQL Server script — or apply it to a database on your own network with the ERD Designer Agent.
What it reads, and what it does not
- It reads
CREATE TABLE,ALTER TABLE … ADD CONSTRAINTandCREATE INDEX: tables, columns, keys, foreign keys, unique constraints, check lists and indexes. Anything else in the script is skipped and listed. - It converts the schema, never the data: no rows are read, moved or changed.
- It does not convert views, stored procedures, functions, triggers or packages.
Which plan you need
Pasting a script and working with it as a diagram is free on the Basic plan, with no card. Converting a diagram to another database is part of the Pro and Advanced plans, which also generate its script and can apply it through the Agent.
Other conversions
- SQLite to PostgreSQL
- SQLite to Oracle
- SQLite to MySQL
- SQLite to MariaDB
- SQLite to Amazon Redshift
- SQLite to Google BigQuery
- SQLite to Snowflake
- PostgreSQL to SQL Server
- Oracle to SQL Server
- MySQL to SQL Server
- MariaDB to SQL Server
- Amazon Redshift to SQL Server
- Google BigQuery to SQL Server
- Snowflake to SQL Server
Questions? Write to support@erddesigner.com. · ERD Designer · Terms · Privacy