October 18, 2013 at 8:22 am
T.Ashish (10/17/2013)
Jeff Moden (10/17/2013)
ScottPletcher (10/17/2013)
Or just:ORDER BY 1
I often avoid using the column names at all in UNIONed queries, as the names somehow seem to
change a lot 🙂 :
Thank goodness that method has finally been deprecated.
+1 for Jeff Moden
Why? Just makes it more difficult to order complex columns and/or UNIONed statements.
SQL DBA,SQL Server MVP(07, 08, 09) "Money can't buy you happiness." Maybe so, but it can make your unhappiness a LOT more comfortable!
October 18, 2013 at 9:25 am
ScottPletcher (10/18/2013)
T.Ashish (10/17/2013)
Jeff Moden (10/17/2013)
ScottPletcher (10/17/2013)
Or just:ORDER BY 1
I often avoid using the column names at all in UNIONed queries, as the names somehow seem to
change a lot 🙂 :
Thank goodness that method has finally been deprecated.
+1 for Jeff Moden
Why? Just makes it more difficult to order complex columns and/or UNIONed statements.
Is as simple as using column aliases from first query.:-)
October 20, 2013 at 12:49 am
Luis Cazares (10/18/2013)
ScottPletcher (10/18/2013)
T.Ashish (10/17/2013)
Jeff Moden (10/17/2013)
ScottPletcher (10/17/2013)
Or just:ORDER BY 1
I often avoid using the column names at all in UNIONed queries, as the names somehow seem to
change a lot 🙂 :
Thank goodness that method has finally been deprecated.
+1 for Jeff Moden
Why? Just makes it more difficult to order complex columns and/or UNIONed statements.
Is as simple as using column aliases from first query.:-)
Even I have never used ordinal position ever, so I'm glad its deprecated.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply