Does Data Compare require records in a certain order to work?

[cmears]

I am comparing two structurally identical tables and the key is a string column that looks like {parent key#}-{child key#}. For example, I have the keys 1-1, 1-2, 1-3 ... 1-14, 2-1, 2-2...2-9, 3-1 .... I am using the Filter to only look at records whose parent keys equal "00160371". So the keys in the table look like 00160371-1, 00160371-2 .... One table has 13 child records and the other has 15. When comparing I should get 13 identical or different (i.e the keys match) and 2 records that are only in the source. Instead I get 5 identical (child keys 1, 10, 11, 12, 13) and 8 that only exist in source (2 through 9) and 8 that only exist in target (2 through 9). So it seems like the comparison orders by the key alphabetically so X-10 comes before x-2. The comparison is fine until we hit -14 and then it goes sideways. Is there some sort of a setting that I have done that makes the comparison think the records must be in order?

[alexa]

Unfortunately, we were not able to reproduce this issue.

Could you please provide us the CREATE definitions of the tables and some data from the tables so we can reproduce this issue on our side?

You can send a reply straight to our support system at supportATdevartDOTcom, so we will keep further correspondence with you on this issue via e-mail.