Bec d'état - Rebecca Scott

Blog | Links | Archive
About | Resume | Advisor profile | Projects | Contact

~/ORDER BY items must appear in the select list if the statement contains a UNION operator

19 Aug 2008

Is a very annoying error message that you get when writing above average complexity SELECT statements. I’m not sure if it only applies to queries against SQL Server, but it can be very difficult to debug if you haven’t come across it before (or come across so many things in a day that they all blur into one big problem).

For me at least it happens like this:

  1. Bec writes a big meaty query, tests it, all ok
  2. Bec writes query #2, which has the same SELECTed columns as the first query, tests also, also ok
  3. Bec sticks a UNION ALL between the two queries, thus making Das Uberquery™ and securing his employment
  4. Bec executes said query and gets cryptic error message, spends rest of day tring to debug 300 lines of SQL, goes home with migraine.

It sounds like one of the queries has an ORDER BY clause but of course I’ve taken all of the ORDER BYs out when joining them, and I’m ordering the UNION as a whole!

The issue is that one or more of the big mutha queries that are being UNION ALLed together contain a subquery that contains a ORDER BY clause. Something like this:

SELECT t1.A, t2.B
SELECT t3.A, t3.B

It’s that ORDER BY Bar part that gives grief. I can’t see why it’s an issue, but this is what to look out for. Replace the subquery with a view or find some other way to do it without the ORDER BY clause.