SQL Formatter Options

Upper/Lower Keywords

These options control letter casing. Most teams settle on one convention – keywords in upper case, table and column names in lower case – and let the formatter enforce it, so that casing never has to be discussed in a code review again. You can also maintain your own keyword list for words the parser does not recognise as SQL keywords.

Upper/Lower Keywords

Lower/Upper Case Options

ID157 acts on the whole statement and overrides the two options below it. Leave it at NONE if you want keywords and identifiers cased differently.

ID	Option	What it does	Default
ID157	ProSelect CASE for complete SQL Statement CASE_STATEMENT	Applies one casing rule to the entire statement. If set to UPPER or LOWER it overrides the two options below, so use it only when you want no distinction between keywords and identifiers. Choices: `NONE` No Change · `UPPER` UPPER CASE FOR WHOLE STATEMENT · `LOWER` lower case for whole statement	`NONE`
ID003	ProSelect CASE for Keywords CASE_KEYWORDS	Casing for recognised SQL keywords. `UPPER` is the most common convention, because it separates the language from your identifiers at a glance. Choices: `NONE` No Change · `UPPER` UPPER CASE KEYWORDS · `LOWER` lower case keywords	`NONE`
ID158	ProSelect CASE for Non-Keywords CASE_NONKEYWORDS	Casing for everything that is not a keyword: table names, column names, aliases. `CAMEL` converts `order_date` to `OrderDate`. Leave at `NONE` if your database is case-sensitive. Choices: `NONE` No Change · `UPPER` UPPER CASE FOR NONKEYWORDS · `LOWER` lower case for nonkeywords · `CAMEL` CamelCase For NonKeywords	`NONE`

ID003 = NONE

Select Dept_Nbr, Dept_Name
From Dept
Where Dept_Zip = '64521'

ID003 = UPPER, ID158 = LOWER

SELECT dept_nbr, dept_name
FROM dept
WHERE dept_zip = '64521'

My Lower/Upper Case Keywords

ID	Option	What it does	Default
ID113	ProMy Lower/Upper Case Keywords CASE_KEYWORDLIST	Your own keyword list, one word per line. Words listed here follow the keyword casing rule even when the parser does not know them – useful for user-defined functions, package names or dialect keywords.	`MyKeyword1`

ID113 contains one word per line, here nvl and decode. Listed words then follow the keyword casing rule ID003.

Not listed in ID113

select nvl(bonus, 0), decode(job, 'M', 'Mgr')
from   employee

Listed in ID113, ID003 = UPPER

select NVL(bonus, 0), DECODE(job, 'M', 'Mgr')
from   employee

Tip: Use this for user-defined functions, package names and dialect keywords the parser does not know. It only affects casing – not linebreaks.

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.