From SQL Source Control 7.1.9, the "Migrations" feature has been removed. This is a significant loss. We're told to use SQL Change Automation instead. But that has additional cost - and is only available as the full SQL Toolbelt.
It would make sense to include SQL Change Automation components, but without the continuous integration parts to replace this loss of functionality.

Have the server name of the database (I.E. DEV, TEST, PRODUCTION, etc.) displayed to the right of the database name.

Create a search filter for SQL Source Control, we can have hundreds of objects in our source control, it would be great if you could search by object name and within the objects themselves on a search filter.

supporting SSDT projects with Redgate Source control will allow developers to use the tool of their choice (Redgate or SSDT) when developing database enhancements etc.

"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.

After linking a DB to Git, I was trying to get back to the Setup Options that are hidden behind the "Setup" tab/button in the top button bar.
The bar was hidden behind the Update banner. As a new user, I didn't even know that bar existed, so I didn't know that I could get there by clicking the "Remind me later" option, until I had opened a ticket with support

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.

I would like to link a local database in SQL Source Control to our Azure DevOps repository. However, as my Azure login has MFA enabled, I am unable to do so. This is a huge pain and I do not want to use GIT as this is a poor workaround to something that should just work (how long has MFA been around?!).

Please add proper support for Azure DevOps to SQL Source Control, including full support for MFA.

When attempting to get latest changes and an error occurs, please be more detailed (e.g table, data, column, etc.) that caused the error that will allow user to correct the error. It is possible the user getting the latest change was the person responsible for the error, making it difficult to trouble shoot when your database is relatively large.

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.

Currently there is not easy way to see or restore a deleted object that was committed. The object code is still in Source Control - but no easy way to see or restore it using SSMS.

This would allow for the option to move the newer revision pane to be on the left and the older revision on the right.

Add snowflake support

Provide the capability to save the users last sort settings. For example on the Commit tab if I sort by last changed by (asd); the next time I go to the Commit tab it should be sorted by last changed by (asd).

SQL Source Control should officially support partially contained databases

To allow us to add SQL Server Agent jobs into source control, allow us to select system tables as static data.
At least dbo.sysjobs, dbo.sysjobsteps and dbo.sysjobschedules in msdb

Make SQL Source Control external to SSMS like SQL Compare. This would allow the developer to use what ever IDE they want to and still commit the changes the same way. I would use SQL Compare to make changes, but it can't do everything SQL Source Control can. Mainly the migration scripts and the pre and post scripts.