Where has TFS changeset notification gone?

Checking for Changes should be possible over multiple Databases on a Server. All Changes on a Databaseserver should be allowed to commit at once.

Add a filter for static data, similar to the feature available in SQL Data Compare. This will facilitate source controlling data for tables that contain a mix of static system data and user content.

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

This would be a comparision between the local version of the files (e.g. loaded from the database) with the latest release on the version control system.

When comparing view definitions from local objects to latest source control version (perforce in our case), SQL Source control doesn't properly read the data compression options from the source control version. So we'll get a difference, showing "WITH (DATA_COMPRESSION = PAGE)" highlighted orange on the left....however the source control file also has this clause, it's just not being read properly. If I check in the file, it will refresh and the same object will still show a difference with source control, even though it's not.

It's far too difficult to find the Filter and Comparison Options items if there are lots of things that might be filtered out or excluded via options. These items should always show on top regardless of the UI sort order because they are so important to synchronize first.

Allow use to set default comparison options e.g. <AddDatabaseUseStatement> rather than have to do it for every individual database linked.

We often restore databases into our working folder and would love an option to simply bring that database up to the latest source controlled version. Right now when we restore a database Source Control thinks we made a bunch of changes so we end up having to "undo" those changes.

I would like to login on any SQL Source Control system using the fingerprint reader.

SQL Source Control will not notice case-only changes to data if the column has a Case Insensitive collation (which is the default out-of-the-box for most SQL Server installations). This bit me when I needed to "sentence case" some "ALL CAPS" data but SQL Source Control didn't even notice until I forced the collation on these columns to be SQL_Latin1_General_CP1_CS_AS, which seems unnecessary. Maybe a per-table static data option?

Need to disable Source Control. It causes way too many errors and slowness. I only actually need to use it once every 2 weeks when we commit our work, but it runs all the time, and causes a lot of frustration.

Provide a mechanism, either internal to SQL Source Control or via Active Directory, to prevent the Delink Database option being selected by any user. This is to ensure that all changes are tracked via SQL Source Control.

When I make a change and for some reason the code is reformatted and keywords are made UPPER CASE, it's almost impossible to see the actual change in the comparison view.

Please if you could just use another color if the only change in a line is about the CASE, it would be much smoother to use the tool.

Thank you for great tools!

When committing changes to source control, the 'Include Dependencies' check box is set to true. Can this default behavior be changed to false?
OR
Can the user have the option to set the default behavior?

Before every commit I have to check in git if the selected branch is the appropriate. It's important and it would be easier, if SQL Source Control showed it.