Answer by Kev Riley
Currently there is no option to do this. It is SQL Servers fail-safe way of generating scripts for YOUR objects, that you might have named with a reserved keyword.
View ArticleAnswer by Steve Jones - Editor
While it might bother you, it's a good practice. It ensures that any strange characters in your objects, spaces, etc., don't cause issues when you run the script. You might think you'll never do this,...
View ArticleAnswer by Phil Factor
I think it is a nuisance, and I agree wholehartedly with the questioner that there ought to be a way to kick it out. Although I have to admit that I occasionally use them when I accidentally use a...
View ArticleAnswer by dvroman
Hate It. I believe there should be something like the VB "Option Explicit" which would explicitly disable any reserved words from being a DB object.
View ArticleComment by Matt Whitfield on Darren 1's answer
That's a bit of a sub-standard approach, as it would blanket remove all square braces, even where they are required for non-natural identifiers.
View ArticleComment by TimothyAWiseman on Darren 1's answer
@Matt, I agree with you, but if the original poster want to disable them then the poster presumably knows that they are not necessary. This is the closest thing to a direct solution to the original...
View Article
More Pages to Explore .....