Thanks all!

actually no I don't it works fine...thanks.  So you can use aliases and in fact looks like you must include the Alias, not the individual fields that make up the...

that works but problem is, then I lose control of whether I want to order FirstName before LastName or vice versa precedence

thanks...

And for this:

>>>We told you the benefits. No headaches when dealing with oddly named objects

well, yea, I guess why would you not use brackets if it was odly named (i.e....

And old QA does it every time.

Automatic tools cannot predict hat kind of names you will use for your objects. So, when it generates scripts it must not give any...

>>And those negotiators not gonna consider your "rule" not to use brackets but make reports unreadable to users instead.

I'm sorry, this is broken English.  Seriously, I'm trying to understand you. ...

OK, so let me sum this up.

Basically it's an all or nothing for me.  I either go with brackets on everything or don't.  I would prefer to go with brackets...

Same with Redgate, everything it creates has brackets, not just reserve words. Now I'm sure RedGate didn't jsut do this for reserve words obviously...

Ok, so all in all, brackets are only for reserved words?  Then how come when you right-click a table or stored proc, and script it, SQL Server put s brackets...

err...thanks, didn't see that one for the ProgramID.  That ended up being it.  Thank you!

you know what it was?  I had to take out the first + after the Char(13) but keep it after the last IF Inner join

TheReligion2000, by my own standards, I have never put a space in for lets say an alias, column name, etc.  So I...

My question was

>>In terms of good practice, should you always bracket field, tables, etc.?  if so, why?

Thanks TheReligion2000

>>why would you need them

well, yea, that was included really in that I would like to know for sure!