UNION ALL returning incorrect results?I recently came across an interesting behaviour when executing queries that included a UNION ALL statement, the examples below were created using SQL Server 2016 Service Pack 1.
Paul Farnell
I am a Database Administrator at Coeo, after graduating from Cardiff University with a degree in Computer Science in 2015, I became a consultant then rotated into database administration. I have a particular interest in optimization and query development. In my spare time I enjoy kick-boxing and the lesser known sport of Korfball.