Another fix would simply be not to change the case of column/table names to the SQL keyword case.

In my case it would even be a far better fix than having the brackets added around these columns as we use to have these column names bracket-free and that's the way our customers write their SQL as well usually.

For a case-sensitive database, the current behavior breaks most of our queries.

This option to add brackets to column/table names which are SQL keywords is very important (not to all fields, only to those which are identified as something else).

I'm working with a database with column names such as VALUE. SQL Complete breaks all the queries by turning it into "value" automatically if we don't put the square brackets manually, and then the autocomplete stops working properly.

It's a major issue for us right now as we use lowercase identifiers (all table names and fields are uppercase) and it breaks all our SQL.

I'm currently using the 1 month demo version to test if SQL Complete could be good for our company (vs SQLPrompt and so on), but this problem is a blocker as it makes us waste time on many of our queries (VALUE is a very common column name in our database).

Option of adding Square Brackets to all Identifiers.

Allow option to add Square enclosing brackets to all identifiers such as "select [Field] from [TableA]"

Enclose objects with keyword names with []

I'm developing with a database where the original developer created some tables and columns using certain keywords. For example, we have a "Resource" table, a "Site" table, and "Version" columns.

When I reference these objects SSMS formats them as Keywords instead of user objects. I can't rename these objects, so my solution to this is to enclose the name in square brackets: []. I was hoping that SQL Complete could do this automatically for me.