InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 21:10:23 GMT20http://www.sqlservercentral.com/Forums/Topic876492-392-1.aspxI just needed to show that your statement[quote]u have to ensure that the aliases of everything your selecting [b]must [/b]match between the top select and bottom select[/quote]is just wrong. Nothing more. But nothing less either.Thu, 04 Mar 2010 16:04:01 GMTLutzMhttp://www.sqlservercentral.com/Forums/Topic876492-392-1.aspxThat's not correct. When using UNION or UNION ALL SQL server will use the alias of the first statement for all. Also, it will use the data type with the highest precedence for all queries.========================================================================A few examples:-- will failSELECT 1 AS aUNION SELECT 2 AS bORDER BY B--if both aliases were the same this wouldnt fail also what advantage is there to having two different aliases because the "b" alias gets lost in the mix. It becomes "a".-- will runSELECT 1 AS aUNION SELECT 2 AS b--no order is being applied here. if a=2 and b=1 it would return 2,1--to your point i suppose there is no reason at all to even alias any but the first select. interesting.Thu, 04 Mar 2010 15:30:59 GMTBaldingLoopManhttp://www.sqlservercentral.com/Forums/Topic876492-392-1.aspx[quote][b]BaldingLoopMan (3/4/2010)[/b][hr]also u have to ensure that the aliases of everything your selecting must match between the top select and bottom select. these aliases is what you will put in your order by[/quote]That's not correct. When using UNION or UNION ALL SQL server will use the alias of the first statement for all. Also, it will use the data type with the highest precedence for all queries.A few examples:[code="sql"]-- will failSELECT '1a'AS aUNION SELECT 2 AS b-- will failSELECT 1 AS aUNION SELECT 2 AS bORDER BY B-- will runSELECT 1 AS aUNION SELECT 2 AS b[/code]Thu, 04 Mar 2010 15:10:04 GMTLutzMhttp://www.sqlservercentral.com/Forums/Topic876492-392-1.aspxalso u have to ensure that the aliases of everything your selecting must match between the top select and bottom select. these aliases is what you will put in your order byThu, 04 Mar 2010 14:55:44 GMTBaldingLoopManhttp://www.sqlservercentral.com/Forums/Topic876492-392-1.aspxIf you still want order by in both querries use inner querry, but ideally using order by at the end of the both querries should also work for youThu, 04 Mar 2010 04:12:37 GMTGiri Dudduhttp://www.sqlservercentral.com/Forums/Topic876492-392-1.aspxRemove the Order By Clause from the first statement and put it only in the last statementWed, 03 Mar 2010 21:28:06 GMTKingston Dhasianhttp://www.sqlservercentral.com/Forums/Topic876492-392-1.aspxI have 2 sql statements and each sql statement is having orderby clause when i am use" UNION ALL " to join them i am getting an error.Wed, 03 Mar 2010 20:16:10 GMTIsmail Ahmed