Last updated: 2026-02-12

Table Designer

Create and modify database tables with a visual interface. Table Designer lets you define columns, set data types, configure primary keys and identity columns, and preview the generated DDL scripts before executing.

Creating a New Table

Use Table Designer to create tables without writing SQL manually.

Opening Table Designer

1. Click More in the toolbar
2. Select Table Designer
3. Or press Cmd+Shift+T (macOS) / Ctrl+Shift+T (Windows/Linux)

Setting Table Properties

1. Select the Database where the table will be created
2. Optionally select a Schema (defaults to dbo for SQL Server)
3. Enter the Table Name (e.g., Products, Customers)

Adding Columns

1. Click Add Column or press the + button
2. Enter the column name
3. Select a data type from the dropdown
4. Configure column properties (nullable, primary key, etc.)
5. Repeat for each column

Column Properties

Each column has several configurable properties:

Column Name

Enter a descriptive name for the column. Follow your database naming conventions (e.g., ProductID, product_id, productId).

Data Type

Select the appropriate data type from the dropdown. Common types include:

Length/Precision

For certain data types, specify:

• Length - Maximum characters for varchar(n)
• Precision - Total digits for decimal(p,s)
• Scale - Decimal places for decimal(p,s)

Nullable

Check Allow NULL to permit NULL values. Uncheck to require a value (NOT NULL constraint).

Primary Key

Check Primary Key to include this column in the table's primary key:

• Primary key columns are automatically NOT NULL
• Select multiple columns for a composite primary key
• Primary keys create a clustered index by default (SQL Server)

Identity / Auto-Increment

Enable Identity for auto-incrementing numeric columns:

SQL Server

• Check the Identity checkbox
• Seed - Starting value (default: 1)
• Increment - Step value (default: 1)

PostgreSQL

• Select SERIAL or BIGSERIAL data type
• Or use GENERATED ALWAYS AS IDENTITY

Default Value

Enter a default value expression:

• 0 - Numeric default
• '' - Empty string
• GETDATE() - Current date/time (SQL Server)
• NOW() - Current date/time (PostgreSQL)
• NEWID() - New GUID (SQL Server)

Modifying Existing Tables

Open existing tables in Table Designer to make changes.

Opening in Alter Mode

1. Find the table in Object Explorer
2. Right-click the table
3. Select Design Table

Adding New Columns

• Click Add Column to append a new column
• New columns are added at the end of the table
• Consider adding a default value if the table has existing data

Modifying Existing Columns

You can modify some properties of existing columns:

Deleting Columns

1. Select the column to delete
2. Click the Delete button or press Delete
3. The column is marked for deletion (shown with strikethrough)
4. Column is removed when you save the changes

Saving Changes

Table Designer generates DDL scripts for your changes.

Preview Script

1. Click Preview Script to see the generated SQL
2. Review the CREATE TABLE or ALTER TABLE statements
3. Copy the script if needed for version control

Reset Changes

1. Click Reset to discard all pending (unsaved) edits
2. In Design (alter) mode the columns revert to the table's last-saved state; in New Table mode the draft columns are cleared
3. Reset is enabled only while there are unsaved changes

Execute Script

1. Click Apply to execute the script
2. Table Designer creates/modifies the table
3. The Object Explorer refreshes to show changes
4. Any open Table Explorer for the same table refreshes its cached schema too — so a newly-added primary key re-enables Edit Mode without restarting the app

Dirty State Indicator

• An asterisk (*) in the tab title indicates unsaved changes
• Modified columns are highlighted
• Added columns show an "add" indicator
• Deleted columns show a strikethrough

Best Practices

Naming Conventions

• Use consistent naming (PascalCase, snake_case, or camelCase)
• Avoid reserved words as column names
• Use singular nouns for table names (Product not Products)

Primary Keys

• Every table should have a primary key
• Consider using identity columns for surrogate keys
• Use meaningful columns for natural keys when appropriate

Data Types

• Choose the smallest appropriate data type
• Use varchar instead of char for variable-length strings
• Use decimal for monetary values (not float)

Frequently asked questions