SQL Formatter Options

Output Format

These options govern the shape of the formatted result rather than any single SQL keyword: how long a line may become before it is wrapped, and which parts of your script the formatter must leave completely untouched.

Output Format

NO-FORMATTING Sections

ID	Option	What it does	Default
ID105	ProNo Formatting between '-- FORMAT_OFF' (iD106) and '-- FORM... NOFORMATBETWEEN	Enables the protected region below. Everything between the two markers is copied to the output byte for byte – the escape hatch for hand-tuned SQL that no formatter should touch.	`on`
ID106	ProSpecify the String to indicate the Start of the Non-Format... NOFORMATSTART	The marker that opens the protected region. Write it in your SQL as a comment, for example `-- FORMAT_OFF`.	`FORMAT_OFF`
ID107	ProSpecify the String to indicate the End of the Non-Formatti... NOFORMATEND	The marker that closes the protected region, for example `-- FORMAT_ON`.	`FORMAT_ON`

Everything between the two markers is copied to the output byte for byte.

-- FORMAT_OFF
select  a ,   b   from  t  where  a=1
-- FORMAT_ON

select b,
       c
from   t2

Tip: The markers are written as comments in your SQL: prefix the string from ID106 / ID107 with --. This is the escape hatch for hand-tuned statements no formatter should touch.

Line Length

ID	Option	What it does	Default
ID022	ProLine Length LB_PAGEWIDTH	The column at which a line is wrapped. The default of 9999 effectively disables wrapping and lets the linebreak options alone decide. Set it to your team's review width – 80, 100 or 120 – to prevent horizontal scrolling.	`9999`

ID022 = 9999 (no wrapping)

select employee_name, dept_name, salary_amount, hire_date

ID022 = 40

select employee_name, dept_name,
       salary_amount, hire_date

Tip: Set this to the review width your team uses – 80, 100 or 120 – so that no formatted statement ever needs horizontal scrolling in a diff.

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.