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. 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 →
  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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  4. I am looking for the report to track who has made the changes and not checked in.

    Hi,

    I need to know who all has not checked in/committed the code the code.

    As we have so many databases to work on and its very hard to see one by one

    Thanks,
    Vijay

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  5. 7 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 →
  6. SourceControl occupies gigabtyes of old files

    Today, my Windows C: device was 99% full. During the search of the biggest files (which were the Windows/assembly/ folder) I noticed gigabytes of SQL Source Control files! Back to Source Control Version 3.x and 4.x even though we already updated to 5.x. Source Control does not clean up old files.

    Directories I found old Source Control files:

    C:\Windows\Downloaded Installations\
    C:\ProgrammData\Downloaded Installations\
    C:\Users\...\AppData\Local\Red Gate\

    Please provide a function do uninstall all those old files that occupy even gigabytes of disk space storage. Thank you!

    13 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 →
  7. Add 'Work Item Number' to the History screen for TFS users

    Add a column in the results for TFS customers so that they can see what Work Item was associated with the changeset

    8 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 →
  8. See incremental changes made before committing

    When working with an object, there is a chance that another developer has made modifications as well since many developers work off of the same database.

    When committing, it would be nice to be able to see a history of modifications. Each time an object is modified (F5) take a commitable snapshot of that object.

    When a developer goes to commit, they could see the different times an object was modified and commit all at one time or commit the individual changes made over time. Doing a commit will roll-up all previous commits made.

    Example:
    Day 1: Dev A: Adds…

    13 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 →
  9. 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 →
  10. Keeping history of locked and unlocked objects

    Locking feature doesn't keep history of who has locked or unlocked specific objects in database. This could become useful when a person unlocks an object locked not by him/her and would help to track historical changes.

    It would require very few changes - additional history table,

    [SQLSourceControl].[LockObject] and [SQLSourceControl].[UnlockObject] procedures would have to be modified.

    Possibly an additional view to see that data in SQL Source Control instead of selecting raw tables.

    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 →
  11. history

    SQL Source Control needs a history view, to be able to view historical Commit/Get updates. A simple list of when/who etc then the ability to see the script used?

    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 →
  12. Strangely "Last changed by" is incorrect.

    I modified 10+ tables by dropping and creating an index. On two tables the index didn't exist and I had to create it. Big was my surprise that those two tables had a different user than me set as the owner of the change. It is even more strange that each table has a different user mentioned as the change owner.

    No big issue, but still something weird. And perhaps better if the change is linked to the user doing the change.

    4 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 →
  13. Embed Coments

    You should consider adding tokens like the following:

    --%version --%
    --%modifications --%

    When you check out the latest version of a SQL Script, Source contral would replace a token in the script with the version history from the repository.
    When the script is checked it additions made in the modifications token are grabbed and included in the comments box for check-in.

    In addition the modification comments could be formatted a little better either by discreet fields or by a masked format.
    Make the message concise and informative. I use the following format:

    [bug/issue number] [Area of Focus] [Action completed]

    Ticket:…

    4 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 →
  14. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  15. Copy history comments in SSMS

    When I am updating my database objects, I'd like to include the version history in my script. I can't copy the version comments into my header block. Perhaps a SQL Prompt like a snippet that pastes the comments into the text editor would work.

    1 vote
    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. Ungroup Source Control Commenting

    Is it possible for the comments window to hold a comment per object rather than as a group? That way I can quickly individually comment multiple objects and check them all in in one go.

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  17. 15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  18. It would be great to see the changes before they are commited to the source control

    This would be a comparision between the local version of the files (e.g. loaded from the database) with the latest release on the version control system.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
  19. Indexed view definitions don't compare with latest version properly

    When comparing view definitions from local objects to latest source control version (perforce in our case), SQL Source control doesn't properly read the data compression options from the source control version. So we'll get a difference, showing "WITH (DATA_COMPRESSION = PAGE)" highlighted orange on the left....however the source control file also has this clause, it's just not being read properly. If I check in the file, it will refresh and the same object will still show a difference with source control, even though it's not.

    4 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 →
  20. Provide Security for the Delink Database option

    Provide a mechanism, either internal to SQL Source Control or via Active Directory, to prevent the Delink Database option being selected by any user. This is to ensure that all changes are tracked via SQL Source Control.

    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 →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base