SQL Formatter Options

ANSI DDL

Formatting for CREATE TABLE and related DDL. A table definition is read far more often than it is written – it is the reference for everyone working with the table – so a stable, column-per-line layout with aligned data types pays off over the lifetime of the schema.

ANSI DDL

Linebreak Before Comma

ID	Option	What it does	Default
ID249	ProLinebreak Before Comma LBB_COMMA_DDL	Leading commas in a column definition list: the comma opens the line of the column that follows. Mutually exclusive with ID250.	`off`

ID249 off (trailing comma)

create table dept
(
    dept_nbr  integer not null,
    dept_name varchar(60),
    dept_zip  char(5)
)

ID249 on (leading comma)

create table dept
(
    dept_nbr  integer not null
  , dept_name varchar(60)
  , dept_zip  char(5)
)

Linebreak After Comma

ID	Option	What it does	Default
ID250	ProLinebreak After Comma LBA_COMMA_DDL	Trailing commas in a column definition list. Mutually exclusive with ID249.	`on`
ID251	ProMove Comma 2 Positions to the left with 1 Space (When ID24... ALI_MOVE_COMMALEFT_DDL	Shifts a leading comma two positions left and puts one space after it. Mutually exclusive with ID252.	`off`
ID252	ProMove Comma 1 Position to the left with no Space (When ID24... ALI_MOVE_COMMALEFTONE_DDL	Shifts a leading comma one position left with no space after it. Mutually exclusive with ID251.	`off`

ID250 off

create table dept
(
    dept_nbr integer, dept_name varchar(60), dept_zip char(5)
)

ID250 on

create table dept
(
    dept_nbr  integer,
    dept_name varchar(60),
    dept_zip  char(5)
)

Brackets

ID	Option	What it does	Default
ID188	ProLinebreak Before '(' LBB_OPENCREATEBRACKET	Puts the opening bracket of the column definition list on a new line.	`on`
ID189	ProLinebreak After '(' LBA_OPENCREATEBRACKET	Starts the first column definition on the line after the opening bracket.	`on`
ID190	ProLinebreak Before ')' LBB_CLOSECREATEBRACKET	Puts the closing bracket on a new line.	`on`
ID191	ProLinebreak After ')' LBA_CLOSECREATEBRACKET	Starts whatever follows – storage clauses, tablespace options – on the line after the closing bracket.	`on`

All four off

create table dept (dept_nbr integer, dept_name varchar(60))

All four on

create table dept
(
    dept_nbr  integer,
    dept_name varchar(60)
)

Indenting

ID	Option	What it does	Default
ID192	ProIndent Cols in Bracket IND_CREATEBRACKETINSIDE	Indents the column definitions one level deeper than CREATE TABLE.	`on`
ID193	ProIndent Bracket IND_CREATEBRACKETOUTSIDE	Indents the bracket itself relative to the CREATE keyword.	`on`

ID192 off

create table dept
(
dept_nbr  integer,
dept_name varchar(60)
)

ID192 on

create table dept
(
    dept_nbr  integer,
    dept_name varchar(60)
)

Tip: A table definition is read far more often than it is written – it is the reference for everyone working with the table. A stable column-per-line layout pays off over the lifetime of the schema.

My CREATE Keywords

ID	Option	What it does	Default
ID195	ProMy CREATE Keywords getting Linebreaks before and after MY_CREATEKEYWORDLIST	Your own DDL keywords, one per line. Each gets a linebreak before and after, which lets you give dialect-specific storage or partitioning clauses their own line.	`MyDDLKeyword1`

With ID195 containing tablespace and partition by, each listed keyword gets a linebreak before and after it.

create table sales
(
    sale_id   integer,
    sale_date date
)
tablespace
    ts_sales
partition by
    range (sale_date)

Option IDs are identical across all SQLinForm editions (VS Code, JetBrains, SSMS, Notepad++, Online Formatter) and are the keys stored inside a profile file. Generated from properties.json 2026.8.21.0.