>> I don't like quoted identifiers and much more prefer bracketed identifiers <<

Why would you actually want to go from ANSI Standards to proprietary syntax? Do you have other scripts to needlessly destroy portability, readability and make maintaining code harder?  

It sounds like the Monty Python routine about nailing bottle caps to your floor so that you can get the feeling of walking on metal bottles in your bare feet ...

I think Joe needs to take some stool softener.  He sounds pretty upset and constipated today.

It's not just today.

And Joe is only the runner-up for being the most cantankerous, contemptible, wretched guy in the database world.

Actually, I agree with Joe -- except for the Monty Python reference -- it was actually Flanders and Swann (At the Drop of a Hat)

Sure, Joe is right some of the time (though not very often), but he's an @$$ all of the time.

Joe -

As far as SQL Server 2005 developers/DBAs using brackets vs quoted-identifiers, it's just plain harder to consistently use quoted identifiers instead of brackets. If you are a "SQL Server only" developer (like me and most likely my fellow Dallasite, Peter, are) you prefer to use brackets. When I develop *my* code for my projects/databases, 100% of the time I'm going to use brackets. If I'm code-managing someone else's code that's only going to use SQL Server, I'll go with the client's convention.

Personally, I would be happy if the standard was modded to include brackets. If you program in multiple languages (C# and SQL are mine), for example, and you want to reference a view that has spaces in the name inside your C#/ADO.NET code, you have to do escaping to reference it with double quotes. Yeeecccchhhh. Is that better? No - it's syntax crap. Brackets should become an optional part of the standard IMO.

What makes brackets easier in Microsoft SQL Server?
(1) Find/replace is a breeze
(2) No need to escape:
SqlCommand myCommand = new SqlCommand("SELECT * FROM "MyView""); // doesn't work
SqlCommand myCommand = new SqlCommand("SELECT * FROM \"MyView\""); // compiles but is crap to write/maintain
SqlCommand myCommand = new SqlCommand("SELECT * FROM [MyView]"); // compiles

It's the same for any programmer of nearly any language. Double quotes are usually an integral part of a programming language and, when you're writing Java/C++/C#/VB/language-of-choice and you need to reference a SQL object that has reserved words/spaces in the name, you either have to escape the double quotes or (if you're *lucky* enough to be using SQL Server) use brackets. I prefer brackets :)