T-SQL field alias options

Question

Is there a best practice or any other compelling reason to use one of these techniques over the other?

Select FirstName
     , LastName
     , (FirstName + ', ' + LastName) As [LongName] ...

Select FirstName
     , LastName
     , LongName = (FirstName + ', ' + LastName) ...

The estimated execution plan looks identical for both so I'm not sure if there is any reason "As [LongName]" is any better or worse than "LongName ="

Answer 1

0

The simple answer is that the AS clause is the ISO standard.

answered May 13 '10 at 02:53 PM

Blackhawk-17
10.5k ● 23 ● 29 ● 34

This is enough reason for me to use As rather than =. T-SQL is moving more towards ISO with each new version. The less code I have to rewrite later the better!

Thanks

May 14 '10 at 09:20 AM user-1783

(comments are locked)

Answer 2

0

or any other compelling reason...

I tend to use brackets for column aliases and = for functions and expressions that tend to be longer such as:

rn = ROW_NUMBER() OVER.... where it is more readily apparent what rn represents instead of having to look at the end of the statement for: AS [rn].

answered May 13 '10 at 07:03 PM

Scot Hauder
5.7k ● 13 ● 15 ● 18

(comments are locked)

T-SQL field alias options

Follow this question

Related Questions