Today I ran into a nice problem with SQL Server fancy way of sorting GUIDS. I know, there should be no reason at all to sort GUID columns but, if what you need is run two tables side by side to check whether they are aligned or not (this is the task of TableDifference) and a GUID is the best key you have, then you will end up ...