SQL Source Control

Welcome to the SQL Source Control feature suggestion list. Find out more information about SQL Source Control at http://www.red-gate.com/products/sql-development/sql-source-control/.

If you have any questions, need help or have found a bug in SQL Source Control, please review our support information http://redgatesupport.red-gate.com/home.

To get new features, performance improvements and bug fixes as soon as they’re available, you may want to turn on frequent updates: http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates

How can we improve SQL Source Control?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Theme in Source Control

    While I know that the "dark theme" is not officially supported in SSMS, it would be nice if Source Control would support whatever theme is selected in SSMS. In fact, I would like to see the theme scheme available across all of the Redgate product family of tools.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. share information about environment between red-gate tools

    SQL Source Control and SQL Prompt may not know about an environment (i.e. a developer not having access to staging or production server) and there's not really a facility in either tool to store information about the version of any environment.

    Thus, SQL Source Control has to ensure backward and forward compatibility when creating migration scripts - which then triggers Code Analysis Errors in SQL Prompt...! It is a mess to clean up, and frankly a waste of time.

    I suggest a feature where I can define my environments in the Tab Coloring in SQL Prompt including a listing of…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Upgrade AppData path when installing Upgrade

    I've been told this is by design: When upgrading SQL Source control from say v5 to v6 all of the source control linked db configs are left behind in the previous AppData folder (%localAppData%\Red Gate\ SQL Source Control 5\ in my example) not moved to the new upgrade version folder (%localAppData%\Red Gate\ SQL Source Control 6\)

    This leaves a history of folders in every users profile, and for us 'from the beginning' users I've got v3-v6 folders that I shouldn't need.

    I'm told this is for Network and rollback reasons.

    I suggest a checkbox or some such thing during the…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  4. Change branches from SSMS.

    If you use multiple branches for a database and you need to switch branches there is no way to change branches in SSMS. While opening some UI for git or using the command line is not difficult it would be nice to just switch to some branch, pull and apply changes, as needed/wanted all inside of SSMS

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Commandline Source control

    It would be great if we could integrate SQL Source Control with our build scripts. For example a simple command line command to get the latest changes and apply (or script) them to our staging environment would be great. Or a command to commit all changes to source control.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  6. Indicate locked objects on the Commit screen

    When we look on the Commit tab at all the changes which have been made to our test environment, it would be useful to be able to see if objects are still being worked on (and who by). Could we have a column next to "Last changed by" to indicate the user who has the object locked?

    For example, if one of our developers is still working on a given stored procedure, they don't want me nagging them to check it in if it is a part of a larger piece of work, which will all be checked in together…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Export / import Link Database configuration setting for shared mode

    It is very hard to do manual database link to repository/SVN if dealing with large number of databases (200 plus within one team) across large number of source control group. Every team member has to spend time and carefully map repository folder.

    One user perform manual link to repository and his/her/ setting validated by QA Team before distributing link config file (xml) to the user group.

    The basic requirement is user should be connected with the DB server and pass the repository path and credential. you may design few screen to navigate and collect user input based on provider input…

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Use Visual Studio or VS Code as a merge tool.

    Add support for manually merging changes in Visual Studio or VS Code instead of KDiff3 or Beyond Compare

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. "Referenced objects are conflicted" message dialog should be scrollable or resizable

    The list of conflicted objects can become so long that the message dialog becomes taller than the screen height. Since the dialog also lacks a scrollbar and cannot be resized, this makes it impossible to click Yes or No when prompted.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Include sys.message custom messages in static data

    The deprecated RAISERROR, and newer THROW T-SQL instructions can use custom (user-defined) messages written into the sys.messages table using sp_addmessage.
    Since these are part of the "source" of a database in SQL Server, and should be syncronised across developers and implemented in production, it would be nice if the custom messages saved in this table can also be added to the static data in a repository.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  11. Option to disable object locking from the GUI

    We have found that Source Control object locking can cause severe lag and even instability in SSMS for distant servers. The additional lag affects the SSMS Object Explorer contextual dialogs (right-click). Often the dialog will timeout and fail to render or multiple tries. Although we are able to disable object locking via the RedGate_SQLSourceControl_Engine_EngineOptions.xml file it would be much nicer to have control from the GUI. This could be in the form of a global on/off switch, or could even add functionality to blacklist certain servers. Alternatively, you could build in some kind of functionality to detect servers with high-latency…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Source Control Migration Scripts - Ability to add before or after main block

    Presently a standalone migration script runs before the main block. This seems odd as the point is to migrate data and for that you need schema to be in place.

    I would like to be able to add standalone migration scripts to the end of the main block.

    We ship databases with some data populated. (This is not simple static data that can be managed using linked tables). We ship for example some out the box entities such as Roles, A base User, a base Organization etc. They have circular references so to insert we have to turn off table…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add support for Azure Data Studio (formerly SQL Operations Studio)

    Azure Data Studio (formerly SQL Operations Studio) is the open source successor to SSMS kind of like VS Code is the open source successor to Visual Studio.

    Please create an extension for SQL Source Control to work with Azure Data Studio.

    https://github.com/Microsoft/sqlopsstudio

    https://docs.microsoft.com/en-us/sql/sql-operations-studio/download

    99 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Option to skip migration scripts on a get latest

    If a migration script has already been run (to rename a table), we don't need to run it again. SQL Source Control is frequently crashing trying to deploy migration scripts and we don't have a way to skip them.

    Can we have a option to skip a migration script when getting latest?

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. migration scripts

    When re-linking databases to source control, there is a warning message about loosing all uncommitted migration scripts, with only a OK/Cancel option. It's seems there should be an option for 'take me to the commit page' so that I can commit those scripts, then re-link.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow SQL Source Control to visualize static data potentially hidden by Row-Level Security

    While comparing static data in SQL Compare, there might occur a "red herring" issue where SQL Source Control cannot see filtered table-data due to being read by a user unprivileged for Row-Level Security. Since SQL Source Control cannot see the table-data, it will then suggest to either

    a) Fetch all table-data from the linked repository (causing all kinds of PK- and other constraint issues)
    or
    b) Commit the deletion of all table-data to the linked repository

    We don't want to do either of these actions. Although bypassing Row-Level Security for an unprivileged user isn't possible, it is still possible for…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow selection of which SSMS instances to install SQL Source Control

    Given the size of our databases, SQL Source Control is VERY slow, frequently locking up SSMS for a minute or more.

    As a result I'd like to (say) use SSMS 2014 for SQL Source Control, leaving SSMS 2017 free to work with.

    Could we please have the option of choosing which SSMS instances to install it against?

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Refresh SQLPrompt after get latest

    After running get latest refresh intellisense and sql prompt cache.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Create a migration script from changesets

    This option is available in version 3. I can see that it is not available in version 5.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add a "Check Static Data" now button to the "Get Latest" tab when auto-check of static data is unselected

    We have a rather large schema with numerous static data linked...
    When I turn off the automatic check of static data, the Get Latest and commit refresh operations take only seconds!! (Awesome!)
    When i turn ON auto check of static data, it takes almost a minute (yawn!).

    It would be really great if I could have the best of both worlds... Do not automatically check static data, but manually check it as I see fit with a separate button on the GetLatest tab that says "check static data now" or something.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base