From: esquel@sommarskog.se   
      
   Plamen Ratchev (Plamen@SQLStudio.com) writes:   
   > The article describes the behavior of using ORDER BY as undefined. Even   
   > recommends the approach that Hugo used as workaround solution (of   
   > course, the query doesn't use ORDER BY):   
      
   The article is certainly a bit confusing. But I prefer to hold on to   
   the first sentence:   
      
      The correct behavior for an aggregate concatenation query is undefined.   
      
   Nevermind that the article then stands on a head to state there is a   
   situation where it works nevertheless.   
      
   And usually it does work. But everyonce in a while, you see posts from   
   people who have been bitten.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
   SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)