SQL Data Compare resorts the files during every check in preventing source control from correctly reporting changes.

1) It prevents us from performing code reviews on data checked in.
2) It prevents us from figuring out who made a change and when without huge efforts.

We have tried to live with this behavior but are finding it extremely frustrating.

When users add a new record, SQL Data Compare first sorts the existing file and then adds the new record to the top of the file. This makes it look like the user is performing multiple actions in source control causing the problems mentioned above. Instead, SQL Data Compare should sort the file AFTER the new record is added, or not at all.