I disagree with most of this article suggests:

1) Entire tablenames as alias make the code harder to read and understand. There's nothing wrong with aliasing an orders table as o, in fact it makes the code more readable. Only in the most incredibly complex join scenarios is is necessary to use more than three characters as an alias.

2) No aliases at all is equally ill advised. Anyone who has used the SQL 2008 Management Studio extensively knows that aliasing a table in even the most simple query lets you take full advantage of intellisense (you get a finite list of the columns in the table after you type the period, rather than a list of all commands that start with that letter interspersed with the column names), whereas if you do not alias your table intellisense does not help you as often and you're more likely to make mistakes. Aliasing all tables with a one or two-letter alias also allows you to avoid future problems when you attempt to add a column to one of your tables later on, and it causes ambigous column name errors.

In fact since SQL 2008 came out I've been aliasing all my table names even in the case of no joins, because I ge the beneift of inaccurate intellisense.