Skip to content

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

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

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

587 results found

  1. No whitespace in file/directory names

    I want an option for all scripts and directories to have no whitespace in their file names. For example "Database Triggers" would be "DatabaseTriggers". This makes working manually with the scripts from the command line much easier.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Prevent UI-reset when "Commit Changes" fails

    When I encounter a problem when attempting to commit changes (e.g. I forget to enter a comment), the UI gets completely reset and I have to reset everything from scratch (not to mention waiting for the comparison to refresh, which takes a long time). It'd be much nicer if a) it prevented me from making a commit with no comment, and b) it doesn't reset all my selections and dialogs.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Object Explorer Details

    Show last history entry (version, author, etc.) per object in the list.
    Create an alternative object explorer style page to do this.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Better importing of existing repositories

    Thanks for the link!

    I've done something similar to this before, but it takes a lot of time and you have to be very diligent. I'm not sure I'm going to go with this route, but just in case someone else is thinking about it, here is the general idea:

    The idea is similar to the link above. You add your db to SQL Source Control (SSC), which creates a new repository/folder, then inspect the folder/file structure it created. You then take your preexisting repository and rename each file to match the same structure as the one created by SSC.…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Installer to offer option to remove older version log folders

    Suggest that the SSCv3 installer NUKE all prior version Log folders e.g., SSCv2 and SSCv1, please...(or at least offer us the choice to have them nuked...) Had Stuart not posted (at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2526239-log-files), I'd have those two folders around for ever...

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Cancel commit clears comments

    If I cancel a commit, on the dependencies dialogue window, it seems to clear the original comments.

    This usually happens if I forget to include an object for commit, and the popup dialogue reminds me. I know it offers to include dependencies I have missed, but this often I'll have meant to include other objects in the submit. If I click cancel to go back and add them, the comments have been cleared

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Need functionality to view user and database objects dependency

    SQL has the feture to view object dependencies. but, it dont have it for SQL logins. So, it will be good to have this feature in this s/w

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Move Column Order

    the ability to move column order
    Example I would like the Owner Column next to the Object Name

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Please make your software more tolerant of slow internet connections with long latencies - like satellite connections.

    Please make your software more tolerant of slow internet connections with long latencies - like satellite connections.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. I am allowed to commit previous changes that upon refresh would show newer changes. Can there be a check for this on commit?

    I want a check on commit for all the items I intend to check in to make sure that there is not a newer version available. In the case where there is, I want to be presented with a list of those changes for review before anything is committed.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Detail the SQL roles required for SQL Source Control needs to commit code

    Provide details

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Selective XML Indexes

    Correctly support SQL Server 2012 Selective XML Indexes (SXI). Currently any SXIs are committed to source control as Primary XML indexes

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Add ability to execute all tSQLt tests before commit, if one or more fail abort the commit

    Add ability to execute all tSQLt tests when committing the database changes, if one or more fail abort the commit and show error messages.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. The undo feature automatically disables your database triggers. I don't want my database triggers disabled.

    We use DB triggers to track schema changes. If we use the Undo feature, it disables the triggers and we no longer are able to record the history apart from our source control system. Source Control is great, but we need to know exactly who made changes and when.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Possible bug: lost check ins?

    Okay, this can be VERY serious! I want to discuss this here in case someone else has similar effects: for several months now (i.e. also in earlier SourceControl versions), we had lost check ins! It occurs very seldom and so far, people said "you just forgot to check it in". But now, several people had the same effect that a successfully checked in stored procedure was just lost! The history does not show the change that the user successfully check in! As this occured about 3-5 times in the last months just for my user account, two other people are…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. Could you please add a feature that would allow one to view the 'dependencies' when on the 'Commit to source control' window appears. It wou

    Could you please add a feature that would allow one to view the 'dependencies' when on the 'Commit to source control' window appears.

    This would be useful to see which of the tables you are about to commit relates to the 'dependencies' tables in the pop up.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Button to script changes, but not commit them

    This is similar to "Allow commits to occur with other code changes," except that if I link to a scripts folder, I have to do that all the time, and I can't ever just commit. I'd like to have the option to commit if what I'm doing is purely in the db (a sp change, for instance), or to just script to the folder if there are application changes also required (like adding a table column)

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. The ability to call source control features in a batch command respective with a command line tool

    We are looking for the ability to commit a set of databases periodically (e.g. nightly) into SVN. So we have a fall back if someone forgot to commit and loose changes on important databases.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Manage setting ChangeLog Database through UI for SQL Server

    The SQL Source Control uses the default trace in SQL Server, however this is stored in the tempdb which can be cleared after a restart.

    RedGate suggest using a change log database as shown in the link here: https://documentation.red-gate.com/display/SOC3/Logging+changes+to+shared+databases

    However, this requires you to manually edit the Engine Options xml file in the user profile, this should be configurable in the UI making setup a lot easier. If you have 10 or more developers it requires that those developers maintain their own Engine Options xml file.

    It would be great if this is configurable through the UI on Setup when…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Track changes as Git does / Support Git reset --soft

    It would be really nice if SQL Source Control allowed commit undo like git reset --soft or tracked the filesystem as Git does instead of tracking commits.

    Scenario that highlights this unexpected behavior:
    - perform some changes on the DB
    - commit changes
    - perform a git reset --soft from command line (undoing the commit while keeping changes on the DB and file system is not possible from the SQL Source Control UI)
    - if further changes are performed from the UI it is possible to commit current changes (old + further changes), but if SQL scripts are changed directly,…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 … 21 23 25 … 29 30
  • Don't see your idea?