The "recently used" lists for both SQL compare and SQL data compare show files for both applications. I find this very confusing, as I have quite a lot of files for both and I have to keep reading the extension to know whether this is a SQL Compare or SQL Data Compare file.

Could we have an option to have a separate "recently used" list for each application, so that I don't see SQL Data Compare files when opening SQL Compare, and vice versa?

Redgate is throwing an error that is costing a lot of our time to be wasted. I can link to source control no problem, but when I go to the commit tab, I see steps 1 through 4/4 complete, then I see the list of changes to check in, but this error pops up and after submitting the error report, the list of changes disappears. I have tried a lot of things and cannot get it to work. Here is what I tried:

Additionally, I got it to link 1 time without the error, and it allowed me to commit the ComparisonOptions.xml file and that was it. I am now trying to link and commit the filter file, and the entire database. Also including a screen shot of the filter file options.

Redgate is throwing an error that is costing a lot of our time to be wasted. I can link to source control no problem, but when I go to the commit tab, I see steps 1 through 4/4 complete, then I see the list of changes to check in, but this error pops up and after submitting the error report, the list of changes disappears. I have tried a lot of things and cannot get it to work. Here is what I tried:

Git requires a commit message by default however SQL Source Control circumvents this setting and commits without a message. There are a few other submissions attempting to get this fixed which have been declined. Seems you are missing the point.

In the case "Empty commit message for git is invalid" the very article you've linked points out that it takes special command line flag to commit without a message. SQL source control commits without a message and provides no mechanism to prevent this. There is no configuration for git that will do this because the default git behavior is already requires a commit message! Unfortunately SQL source control is subverting this. Please stop subverting the default git commit behavior or provide a setting to enforce a commit message...

Git requires a commit message by default however SQL Source Control circumvents this setting and commits without a message. There are a few other submissions attempting to get this fixed which have been declined. Seems you are missing the point.

In the case "Empty commit message for git is invalid" the very article you've linked points out that it takes special command line flag to commit without a message. SQL source control commits without a message and provides no mechanism to prevent this. There is no configuration for git that will do this because the default git behavior is already…

Locking feature doesn't keep history of who has locked or unlocked specific objects in database. This could become useful when a person unlocks an object locked not by him/her and would help to track historical changes.

It would require very few changes - additional history table,

[SQLSourceControl].[LockObject] and [SQLSourceControl].[UnlockObject] procedures would have to be modified.

Possibly an additional view to see that data in SQL Source Control instead of selecting raw tables.

from http://country.io/continent.json you can have both countries to contenents and give Countries valid cities eg http://country.io/capital.json Which means if you can defined a key-value pair you can create more accurtate test data that placing "St Petersburg" in "Iceland" which is the current option.
At worse if the json file was downloaded and 'mounted' as a table would be useful. But really JSON is the new datasource that Red-gate has to connect to.

With Amazon RDS, the server names are changed each time an instance is created. If a dev instance is recreated monthly, and a testing instance is recreated daily, it is impossible to keep the connection to source control when the server names change.

The only way to get source control to work with our system is if it were able to connect to a static end point (dns record) rather than the server name itself

Source conrtol should be a standalone app not SSMS addin. When performing get latest or commits, on large environments and slow connections this can easily take 20 minutes during which a click anywhere else in SSMS restarts the get latest/commit process. The logical use of source control being a SSMS addon has been outlived.

When using either SQL Compare or Data Compare, during deployment, can we have an option to supply and store a static name for the script file rather than having to overwrite script file name in each deployment. You could supply an option to automatically overwrite the file. For early development I want one script only, I don't need to maintain a history, especially if I'm going through the deployment testing phase.

It would be great if we could have a product manager for SQL Toolbelt and or individual products we're licensed for. In the manager you could see which products you have access to, which ones that are installed, view the VS and SSMS versions installed in your local system and install/uninstall products to the VS and SSMS versions. This would be similar in operation to the Telerik Control Panel which provides this kind of functionality.

I have a bunch of Ruby services which talk to sql server. I'd love to be able to stand up and tear down databases for development using Microsoft's mssql-server-linux docker container while still managing my database via Redgate. This would require a linux-based CLI tool that could create the database from source.

I like how SQL Source Control can show you that there is an uncommitted change to an object with a blue dot on the object. Could this be built upon by allowing users to right click on the object and then have an option there to show a diff between the current code and what is committed to source control? This would be the same results that you see when you go to the 'Commit' tab and select an uncommitted object. It would be very helpful to see that comparison easily.

SQL Source Control doesn't recognise changes to objects when the only change that has been made is in comments. The change is marked in object explorer when initially made, but clicking refresh in the source control window then ignores the change and removes the indication that the object has changed. There doesn't appear to be any setting to remove this filtration. The only other option is to alter the object's functionality or definition, commit, then change the definition back and re-commit. This is inherently risky, and should be unnecessary.

We use comments as a key part of our system documentation, and I'm sure they are integral to many other developers too, so it makes no sense not to be able to commit these code changes.

SQL Source Control doesn't recognise changes to objects when the only change that has been made is in comments. The change is marked in object explorer when initially made, but clicking refresh in the source control window then ignores the change and removes the indication that the object has changed. There doesn't appear to be any setting to remove this filtration. The only other option is to alter the object's functionality or definition, commit, then change the definition back and re-commit. This is inherently risky, and should be unnecessary.

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

Someone in my team linked one of our test environment's databases to his source control. He was in a feature branch and just performed a "Get Latest" on the dB..... Now we have to reimplement the integrated changes. Please display the Server name in the setup window to avoid confusion and make sure this is clear.

ReadyRoll looks great but one of it's downsides is that you have to use Visual Studio. If mostly work gets done using SSMS, then switching to Visual Studio is not a great experience.

Both ReadyRoll and SQL Source Control use the same comparison engines, they both output objects as files on disk and support migrations.

To satisfy both worlds (making great experience when using Source Control on SSMS) and have a proper way to automatically update databases from source control files using migrations (like ReadyRoll does), SQL Source control should integrate with ReadyRoll - after each commit, a migration script would be generated, .sqlproj created or updated. Sql Source control would need some additional options (such as pre-deployment or post-deployment scripts), shadow DB options for comparison, etc.

ReadyRoll looks great but one of it's downsides is that you have to use Visual Studio. If mostly work gets done using SSMS, then switching to Visual Studio is not a great experience.

Both ReadyRoll and SQL Source Control use the same comparison engines, they both output objects as files on disk and support migrations.

To satisfy both worlds (making great experience when using Source Control on SSMS) and have a proper way to automatically update databases from source control files using migrations (like ReadyRoll does), SQL Source control should integrate with ReadyRoll - after each commit, a migration script…

During a data-refactoring effort, I accidentally created a query that looked like this:

SELECT *
FROM Customers
JOIN Orders o ON o.CustomerId = o.CustomerId

Obviously, this is wrong, and results in a cross join. It would be great if SQL Prompt could produce a warning when:
1. ON clause compares a column to itself
2. ON clause does not reference the table being joined to

In the commit tab you can see the differences between source control and the database which makes it great for deciding what you want to commit or rollback. If you select items in this tab and them right click and undo changes your selections are lost and you have to re-select in the Undo Changes dialog which doesn't let you see the change.

As a developer I want to be able to see the change that I am about to undo.

'Please ensure that the service is started. Click here for more information about this problem.'
How about fixing this bug for when source control have forgotton its lic, which of course is fine . you can then try deactivating and reactivating, it says its is ok but nothing has changed. Would be so nice to be able to log on to your subscription, and tell it 'USE THIS ONE' so it can see on a redgate site what lic to use.