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 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 →
  2. 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 →
  3. 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 →
  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. 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…)
  6. 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 →
  7. 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 →
  8. 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…)
  9. 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 →
  10. database properties

    Redgate still does not Support Database properties??

    They shuold support properties like (Transaction Isolation level (Read Committed, Snapshot)Ansi Null, Quoted Identifier). These are Crucial. I cannot believe these are not in source control yet. The product has been out since 2006.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Disconnect the SOC pane from Object Explorer

    Right now the SOC pane is linked to the database in Object Explorer. The problem in this is that the pane can't work asynchonously to get changes while I move on.

    Give the slow performance of looking for changes and populating the commit tab, can we

    1. Put a drop down in the SOC pane to choose the db
    2. Have the Commit popular process (refresh) be set to work with this database asynchronously. Either allow me to set a polling interval or click the refresh button, but then allow me to move to another tab and continue to work. …

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Generate a Script rather than Apply changes in the Get Latest tab

    I am using GIT and SQL Source Control. After running "Pull from remote repository" in the Get Latest tab, the only option is to Apply changes which directly updates the database.

    If the changes include something like the classic renaming of a column, it will drop the column and add a new one and I lose data.

    I would like to be able to simply generate a script so I can review it and manually apply it rather than directly update the database.

    17 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Custom Formatting

    Allow for custom formatting used by SQL Prompt to also be used when committing code with SQL Source Control.

    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 →
  14. Changing a data type used in a SP creates problems

    When changing a data type used in a SP (e.g. add a new column to it and commit it). getting latest fails on other linked DBs. You have to drop the SP on the target DB.
    The weird thing is that sometimes it works, but most of the times it doesn't. Not sure why the behavior is not the same all of the times...

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Enable quick access to the source control log

    Currently accessing the log of the version control system is very slow.
    On a good computer it takes me 20 seconds to open the view history from your menu.

    To open the same log through tortoise svn it takes me 2 seconds to lokate the ex. "Open working base" under the "Under the hood menu" in Setup and 1 second to launch the tortoise SVN log viewer for the project.

    Could you please consider adding a possibility to either open the history quicker, or alternatively allowing the user to open the version control log in an external viewer.

    Maybe there…

    3 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 →
  16. 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 →
  17. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 →
  20. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 28 29
  • Don't see your idea?

Feedback and Knowledge Base