I am not able to push changes to my repo using SSH because I am unable to enter my passphrase. I have to push/pull using Git Bash.

I would like to see support for the git worktree feature. We often need to work on multiple branches at the same time, and this would help.

I see someone else has also asked about this as a feature on your forums. (https://forum.red-gate.com/discussion/86826/is-it-possible-to-support-git-worktree-feature-for-sql-source-control)

Issue: In most cases, committing changes from the Commit tab marks 'Action' in SVN logs as 'Replacing' than 'Modified'. This is creating a major tree conflict and related problems for us when trying to merge changes between branches.

Suggested feature: add option in settings to change this behavior so that Source Control will always do 'Modified' for existing objects than 'Replacing'.

https://productsupport.red-gate.com/hc/en-us/requests/165651

Please add the ability to create Pull Requests directly from SQL Source Control. In our environment, we require that any push to even the develop branch from a feature or bug branch requires a pull request.

Would be good if there was a checkbox to ignore replicated objects. If in the context of the DB (without going to the [distribution] database) you can't tell which objects are replicated, then at least an option to exclude the transactional replication spMSins%/spMSupd%/spMSdel% procedures without having to explicitly add them to the filter.

Hi - we use git in Azure DevOps. I have a few options for cloning,

1. command line (which tbh i dont use much),


2. 'git gui' - which is reliable and easy


3. clone using visual studio from azure devops which doesnt work too much.

it would be nice to be able to do the clone from the redgate sql source control GUI though

ALSO

When linking the database it would be nice to have a shortcut to

c:\users\username\source\repos - this is where visual studio seems to default to and is a pain to browse to each time.

for a number of databases we have a lot of post-deployment steps - basically to add conditional data to tables (that cant be solved by table linking) or adding SQL Jobs.
Currently this can all be thrown in a post-deploy script, but this makes it monolithic and much harder to see changes in objects.

SQLCMD syntax would solve this problem (:r .filename.sql), but even executing everything in the post-deploy directory in alpha order would make the post-deploy much more manageble

We use SQL Source Control with TFS. It would beneficial if we could tie multiple task IDs to one commit and all changes would in one change set.

ExamDiff pro is an excellent compare tool with merge facilities. See https://www.prestosoft.com/edp_examdiffpro.asp.
It would be great if SQL Source Control also supported this for merging.

A good alternative would be to allow any “external merge tool” to be used for merging, where the application, and arguments can be specified.
The latter option effectively should support almost any merge tool, including WinMerge and UltraCompare

I love Redgate toolkit and SQL Source Control, but would like to integrate it into other tools and processes. Creating a CLI or Powershell (PS) module that allows users to check a database for changes and check in those changes from the command line would be awesome. I am already going to PS to create branches and it would be nice to just check in my change while I'm there.

I would also love to see the ability to manage DB connections for SSMS, VS and VSCode in one location.

Instead of having to address each database separately to link to SOC, why not have an option on the SQL Server instance to right-click and "Link All" databases in one fell swoop.
We plan to implement SQL Source Control and hundreds of databases need to be linked to SOC. We have been directed to some Powershell options which are supposed to link all databases automatically but that option is not working at our installation

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