If you have a HiDPI or 4K display, SSMS is scaled to 2x. In SQL Source Control, The Commit and Get Latest tabs are fine, but the Migrations, Locking and Setup UI are scaled MUCH larger than 2x. I would prefer those UIs be scaled to 2x.

It is not possible to resize the columns on the Migrations tab. This makes it difficult knowing which objects to include when creating new migration scripts as most of the names are truncated.

If I exclude items from source control they should not default to be committed due to dependencies. It would be great if there was a setting when items are excluded to never include them in the list of items that are dependencies.

Get rid of the option for anybody to unlock an object, but instead allow to unlock only by the person that locked the object or by a group in group role in the database where only few people have access.

Sometimes I'm connected to multiple instances and it would be nice if the Source Control tab made it clear which instance I was about to change or commit from.

SQL Source Control needs a history view, to be able to view historical Commit/Get updates. A simple list of when/who etc then the ability to see the script used?

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

It would be nice to be able to create and checkout a branch form the SQL Source Control UI instead of having to switch to the VCS client.

Same idea as
https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/5400202-sql-compare-store-options-for-index-create-rebuild

The blue circle indicating changes to be commited should auto-refresh (added/removed when necessary) and refresh when the SQL Server refresh icon or menuitem are clicked.

Now it only refreshes when the user goes on the Commit or GetLatest tab.

Using the latest verrsion I cannot create a migration script for selected changes (checkins in the versioning control system).
The menu option it had in the database context menu is missing.
Why did you remove this feature?
It was nice for allowing migrating environments that you cannot connect to.

We use GIT hosted under TFS in order to use Windows authentication to protect the GIT repositories.

SQL Source control does support a local copy of the GIT repository but remote Push and Pull fail in SQL Source Contrtol 5 because it cannot handle the login dialog needed to get to GIT

When doing a Get Latest in SQL Source Control, if database is registered in DLM, then register the known schema from SQL Source Control

I modified 10+ tables by dropping and creating an index. On two tables the index didn't exist and I had to create it. Big was my surprise that those two tables had a different user than me set as the owner of the change. It is even more strange that each table has a different user mentioned as the change owner.

No big issue, but still something weird. And perhaps better if the change is linked to the user doing the change.

Add option like SQL Search application for quick acces to object

High DPI screen scaling doesn't work well with SSMS 2016 RC3.
The source control screen doesn't fill the entire work area, but just takes up a small rectangle in the top left (approximately 50% x 50% of the work area).
This occurs on a 3840x2160 pixel screen, SSMS version 13.0.14000.36, red gate source control version4.4.0.1714 standard

Please give option for DML trigger changes be tracked separately from tables. It's very annoying trying to support and enhance a trigger-heavy inherited database that needs an extensive trigger optimizations. It doesn't allow me to isolate and rollback my changes very easily ... and branching and integrating - ha! This was almost a big enough deal to send me to ApexSQL... alas, I am regretting my decision these days. It seems people have been requesting this feature in Source Control and Compare for a while... please stop pushing it aside - it's frustrating. Thanks