Earlier versions would maintain the Where Clause when it was the same for multiple selected tables. We have a project that never changes other than one part of the where clause but I have to re-enter the same where clause every time. It's only saved per individual row.

When we upgrade an application, say by adding tables, we use frequently use SQL Data Compare to move the data from the old database to the new, upgraded database. It would be great to be able to migrate the CDC data for the tables in the original version of the database to the new version!

when expecting a perfect match, please provide an option to halt the compare after a user-provided number of mismatches.

SQL Compare can exclude tSQLt-related objects. SQL Data Compare should have a similar facility, at least for parity with SQL Compare and also to reduce false positives in the result

In SQL Data Compare, when I click on the box to show Value details, the box pops up just fine. However, I really really want it to close when I hit Escape. Having to actually 'X' out of that box bothers me. I may have dozens or hundreds of records I need to check quickly, and it takes so much longer.

My notebook was stolen and I can't deactivate my existing licence. Please help!

When i am comparing tables with binary data i am limited to Ansi or Unicode Text, Hexidecimal or Picture. We are storing PDF, Word and HTML documents and i would like to be able to view those better to see the differences. If this is not possible how about an export to open the data into the actual application (like an "open with....." option)

Support Azure AD auth using MFA

When updates are available, you cover part of the header. Please do not cover this information. (screen shot available upon request)

An option for trailing white space does already exist. Unfortunately there is no option for leading white space yet. This would be very useful and propably is no big deal to implement.

If you have a project with a bunch of table and view mappings configured, you can easily switch between (similar) databases and retain those mappings. However, if you switch from the database type to the scripts type, even if the schema is basically identical, any mappings with filters get unchecked, but the rest remain selected. RedGate silently makes this change, and it should be considered a bug. Let me choose which action to take. If you try to re-enable those mappings, the filters are only applied to one side of the comparison, which is also an issue.

When creating deployment script, would like the option to select from the list of dependencies rather than all or nothing.

I need to compare and sync history of temporal tables as well when testing our system in different environments. Competitive products already have this feature.

Sometimes when copying data from server to server I need to change soemthing in the deployment script (e.g. replace a guid with another guid for a FK to work). Please allow editing the script before running it through Data Compare (currently I have to copy it, edit it and run it manually)

Currently, the Export CSV includes Matched and UnMatched field. It would be good to only see the UnMAtched Fields so quick action can be taken to fix it. It's especially painful when you have a table with a lot of fields and only a few are unmatched.

This feature is currently only available inside the tool. See https://us.v-cdn.net/6029854/uploads/editor/1m/d9ozpaupqkzc.jpg

Allow data from one source table to be mapped to 2 or more destination tables. Due to requirement changes we needed to split data from one table in to two separate tables but data compare will only map one source table to one destination table. Some data has to be duplicated on both tables and some belongs to one or other of the new tables.

Its great that you can tell if xml columns are diffierent. But please improve the ablity to view the doc and see the differences. Being able to save change would also be great.

Today, empty tables that have no rows appear in the list of "xxx tables or views with identical rows only". It would be more accurate to split this list into tables/views with data that are identical and table/views that are empty.