Designers
functionalVisual object designers for building and altering database objects without hand-writing DDL.
Visual designers for building and altering database objects, so routine structure work does not mean hand-writing DDL and hoping you got every clause right. There are three related surfaces:
- Designers - a create-new dialog with Table, Index, and Foreign Key tabs. Tables get a column grid (name, type, NULL / Identity / PK checkboxes); indexes get key and include columns, a filter clause, fill factor, and unique/clustered flags; foreign keys get the child and parent sides. A live preview shows the resulting DDL - green when valid, or the reason it is not, and Script to Editor hands it to a tab. Nothing runs from here.
- Edit Structure, an ALTER designer for an existing table, with Columns, Indexes, and Foreign Keys tabs and a live change-diff instead of raw SQL. It knows the engines' quirks: MySQL exposes
ALGORITHMandLOCKchoices for online DDL, and PostgreSQL type changes get aUSINGcast filled in automatically. Also script-first. Object properties - - a paged property editor for thirteen object kinds, from server down to column, with rename and nullability edits. It is the one designer that can execute, and only behind a Review changes sheet that shows the exact SQL with Copy / Cancel / Execute. Engine coverage: the guidedDesigners
CREATE TABLE … ENGINE = MergeTree in a query tab). Edit Structure works on SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, libSQL / Turso, DuckDB, ClickHouse (where it covers ADD / DROP / RENAME / MODIFY COLUMN and data-skipping indexes, and flags key changes for manual review), and Oracle Database (Oracle's own ADD, MODIFY, DROP and RENAME COLUMN and constraint changes). Redis keys have no structure to edit.

