on my system, the query plans show no ordering before the TOP 1 is
applied. That explains everything.
My guess is, that it has something to do with the fact that it is a
heap, because adding a (clustered) primary key to the table caused
SQL-Server to return the correct results.
Nonetheless, the results are incorrect, which means it is a bug.
Delbert Glass wrote: