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. Add the ability to swap the compare panes poistions in the View History Window

    This would allow for the option to move the newer revision pane to be on the left and the older revision on the right.

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make SQL Source Control external to SSMS

    Make SQL Source Control external to SSMS like SQL Compare. This would allow the developer to use what ever IDE they want to and still commit the changes the same way. I would use SQL Compare to make changes, but it can't do everything SQL Source Control can. Mainly the migration scripts and the pre and post scripts.

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Better Git performance

    While it is great the SSC supports Git, I have found that when connected to a large repository, SSC can take forever to commit or do a get latest.

    I have also noticed that the working base and transient folders can grow quite large as the whole Git repo is cloned into these folders. I have had to periodically go in there and have Git compress it's objects so that I can reclaim some disk space.

    I imagine that the performance of SSC is related to the size of the Git repo and I just feel like there is room…

    20 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. snowflake

    Add snowflake support

    9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. add option to view commited deleted object code from repsostiry in SSMS

    Currently there is not easy way to see or restore a deleted object that was committed. The object code is still in Source Control - but no easy way to see or restore it using SSMS.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →
  6. Separate comparison options for "Ignore tSQLt framework" and "Ignore tSQLt tests"

    Currently, SQL Source Control and SQL Compare have an option to "Ignore tSQLt framework and tests". We want to create our tests in dev and include them in our stage deployments for regression testing. The current setting ignores the framework AND our custom test code.

    We want the Red Gate tools to ignore only the framework, but not the custom tests. We will manage the framework install separately. Ideally, there would be separate ignore checkbox rule options, one for the framework and another for our tests.

    We have to set the current option to unchecked ("don't ignore") and then set…

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    88 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. SQL Sourse Control Sort Option

    Provide the capability to save the users last sort settings. For example on the Commit tab if I sort by last changed by (asd); the next time I go to the Commit tab it should be sorted by last changed by (asd).

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. 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

    18 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Partially contained databases

    SQL Source Control should officially support partially contained databases

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Agent jobs could be source controlled if we were able to select system tables as static data.

    To allow us to add SQL Server Agent jobs into source control, allow us to select system tables as static data.
    At least dbo.sysjobs, dbo.sysjobsteps and dbo.sysjobschedules in msdb

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  13. Keep Static Data Stored in PK Order

    When storing the data items in files, it would be good to keep everything in PK order so that changes are easier to spot. Historical order is less important when working with static data.

    90 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Data warehouses need source control too! (Azure SQL Data Warehouse / PDW)

    Add source control support for Azure SQL Data Warehouse. I'd love to be able to source control my data warehouse schema.

    34 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Source Control Standalone instead of SSMS snapin

    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.

    58 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Support Azure Active Directory Authentication

    This has over 50 votes but its in SQL Prompt. This is a HUGE pain for us as we need to use AD to adhere to security policy.
    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/15008409-add-support-for-azure-active-directory-authenticat

    150 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Azure  ·  Flag idea as inappropriate…  ·  Admin →
  19. require a commit message for git

    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…

    24 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Option to use modification date as the commit date

    With SQL, when you modify an object, that object is now out there to be used or tweaked by other developers. Committing it is really just a statement of, I'm done working with this object and here's what I've done.

    We have the problem of not committing objects as timely as we should. We make a modification and go our way until we realize a week later, we forgot to commit. So we commit, but the date time stamp of the commit is not helpful. That is just when the developer remembered.

    I think it would be much, much more…

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 28 29
  • Don't see your idea?

Feedback and Knowledge Base