I've noticed that Visual Studio 2008 is placing square brackets around column names in sql. Do the brackets offer any advantage? When I hand code T-SQL I've never bothered with them.
Example: Visual Studio: SELECT [column1], [column2] etc...
My own way: SELECT column1, column2 etc...
In addition Some Sharepoint databases contain hyphens in their names. Using square brackets in SQL Statements allow the names to be parsed correctly.
The brackets are required if you use keywords or special chars in the column names or identifiers. You could name a column
[First Name]
(with a space)--but then you'd need to use brackets every time you referred to that column.The newer tools add them everywhere just in case or for consistency.
During the dark ages of SQL in the 1990ths it was a good practice as the SQL designers were trying to add each word in the dictionary as keyword for endless avalanche of new features and they called it the SQL3 draft.
So it keeps forward compatibility.
And i found that it has another nice side effect, it helps a lot when you use grep in code reviews and refactoring.
They are useful if you are (for some reason) using column names with certain characters for example.
would not work, but putting square brackets around the column name would work
In short, it's a way of explicitly declaring a object name; column, table, database, user or server.
The brackets can be used when column names are reserved words.
If you are programatically generating the SQL statement from a collection of column names you don't control, then you can avoid problems by always using the brackets.
I believe it adds them there for consistency... they're only required when you have a space or special character in the column name, but it's cleaner to just include them all the time when the IDE generates SQL.