SQL Syntax Formatter

This is great thread to use in CLASS and lectures :-)

I used to keep some of those type of threads in order to explain people why you should use a good naming format :-)

Personally I think this is your designer/architect fault and you pay now for the mistakes, I highly recommend to learn from this, and use this time of upgrade to make some changing, if you can spare the time.

I don't think there is a problem with good naming format or to blame the DB architect because of syntax compatibility. They will never know that the keyword will be incompatible with newer version until it released. In this case, "EXTERNAL" keyword was okay in SQL 2000, but not okay with SQL 2005. They already did their job to make the column name readable and understandable.

I don't want to blame SQL 2005 (and later versions) as well for this case, and that's why we decided to use square brackets to avoid this kind of problem in the future.

Thanks for your suggestion to make small c# application, we will consider this option to tidy up the code.