Today, I worked on a service request that our customer asked about how SQL Server sorts the uniqueidentifier data type. We know that uniqueidentifier store globally unique identifiers (GUIDs). GUIDs ...
You've stated that your sorted list of GUID's comes out as:
6682BC4F-949E-478F-BBA2-0003C71CD035
A6D423B8-07F3-4F13-B34E-0004DC3317B7
C2EB258A-147F-4F26-97D7-0000F053CCA8
EE2C394E-7AB0-468F-B959-0005C0CC598D
But that's not how SQL Sorts GUID's. And your first example with DecomponerString() shows that. You sort by the GUID value - and you get a completely different sort order to what you get when you sort by your generated string. The real sort order is by byte group from right to left.
If your two examples with DecomponerString() actually worked - the sorting between the two should be the same.
Microsoft
