Each dialect has its own keyword list, quoting rules and function names. Formatting a T-SQL query with standard-SQL rules can leave bracket-quoted identifiers like [Order] mis-indented, and PostgreSQL constructs such as DISTINCT ON or :: casts are only recognised by the right parser.
Should SQL keywords be uppercase?
It is a convention, not a requirement — SQL keywords are case-insensitive. Uppercase keywords with lowercase identifiers is the most widely used style because it makes the query structure scannable at a glance. Some modern teams prefer all-lowercase; both options are available.
Will formatting change what my query does?
No. Only whitespace and keyword casing change, and neither is semantically meaningful in SQL. String literals and quoted identifiers are left untouched, so data inside quotes is never reformatted.