A tabular visualization with the differentiation between "added" (only in database), "changed" (on both sides existing but with different data) and "removed" (only in repository) would help to check the differences and with a possibility to select certain differences which should be committed, it would also be more efficient that different developers can commit only their own changes on a table, which is linked regarding static data.
In addition a possibility to hide the unchanged columns in the tabular visualization would also be really good.

"Take theirs" and "Keep mine" are an all or nothing option, I would like to have more control over this and be able to keep my new records but take the updated, or keep my updated records but take the new records, for example.

With 100s or 1000s of tables it becomes quite tricky to find objects in the static data link / unlink UI. Therefore, I suggest adding a search textbox there as well as making the UI columns (name, key, schema) sortable.

When displaying the Static Data differences in SQL Source Control it would be very useful to show the number of records that are Different/Identical/In Database Only/In Source Control Only.

When tables have thousands of records it can be difficult to know the scale of what you’re about to check in or get by just scrolling down a long list. A tab displaying the records for each distinct group would be even better.

It would be great if we could integrate SQL Source Control with our build scripts. For example a simple command line command to get the latest changes and apply (or script) them to our staging environment would be great. Or a command to commit all changes to source control.

The deprecated RAISERROR, and newer THROW T-SQL instructions can use custom (user-defined) messages written into the sys.messages table using sp_addmessage.
Since these are part of the "source" of a database in SQL Server, and should be syncronised across developers and implemented in production, it would be nice if the custom messages saved in this table can also be added to the static data in a repository.

We have a rather large schema with numerous static data linked...
When I turn off the automatic check of static data, the Get Latest and commit refresh operations take only seconds!! (Awesome!)
When i turn ON auto check of static data, it takes almost a minute (yawn!).

It would be really great if I could have the best of both worlds... Do not automatically check static data, but manually check it as I see fit with a separate button on the GetLatest tab that says "check static data now" or something.

We are using System Versioned Tables, and on these tables SQL server adds 2 new columns SysStartTime and SysEndTime. These columns are typically marked as hidden and we need a way to ignore comparison for these. Either by a column level filter, or an option to ignore system versioning columns

I would like to be able to pause/start scanning a database for changes as will. It is trying to do several at the same time right now and one of them is huge which is taking longer than it should. If I could only scan the one I am working with at the moment it would save me time system resources.

The open in excel feature is impressive and I love to use it for ad-hoc extracts. Having the ability to extract multiple results in 1 go to a single Excel file with different sheets would be great.

When linking static data to source control the unicode characters are appearing as question marks
so please add the support for the unicode characters in the script files

Sometimes I need to write scripts to run before and after a SQL Data Compare.

After we have run a restore database command, the source control do not notice, that some, earlier loaded stored procedures from lastest version are after that newly out of date.
Source countrol should recognize a restore and scan completely new for the latest changes.

When adding a static data table to source control, there should be a warning if that table has a foreign key constraint on another table and give the option to include that table as static data also. As it is the error you get in SQLCI is quite hard to decipher when SQL Source Control is used in conjuction with SQLCI.

If a table is setup for static data, and you remove one or more columns from that table, the static data is not updated in the working directory when "Saving changes".

allow copy names from result Cell by Cell
Like if we want to copy only object name it should allow.