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

179 results found

  1. Integrate with Fortress Item Tracking

    When checking in changes allow the user to link the changes to a Ticket ID in Fortress Item Tracking, adding a comment to that ticket and adding the ticket ID/details to the checkin comment. Also optionally allow the user to complete the ticket when checking the changes in.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Support Additional Source Control Systems  ·  Admin →
    completed  ·  Gyorgy Pocsi responded

    Using the latest Vault EA build (1.1.3.49) it’s possible to connect a commit to a ticket id. An example comment you could use to mark bug id 4 as completed:

    Fixing that old bug #4 #completed

    You can use any status string you have in use instead of completed.

  2. Handle Getting New NOT NULL Columns

    In a dedicated development model where each developer works against their own copy of the db, if my co-worker adds a new NOT NULL column to a table, the get latest script will fail for me since my table contains data and NULLS are not allowed in this new column.

    Please comment on how you would like to see us handle this?

    5 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…)
    2 comments  ·  Admin →

  3. Support "Require BugID For Checkins" option for Vault

    In SourceGear Vault there is a repository setting that forces the user to enter a BugID when checking in changes "Require BugID for Checkins".

    SQL Source Control doesn't seem to honor this setting. It doesn't prompt you for a BugID, nor does it stop you from committing changes despite not having a BugID.

    We rely on that feature, and would really like to see it incorporated into SQL Source Control.

    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…)
    2 comments  ·  Admin →

  4. Make it faster!!!! Improve Performance!!!

    Oog, each commit is like five minutes. Neither standard commits of source code (same SVN server) nor redgate SQL Compare actions (same local database server) take that long!

    Keywords: Performance, Speed, Fast

    312 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…)
    46 comments  ·  Admin →
    completed  ·  AdminStephanie (Product Manager, Redgate) responded

    We have been doing a lot of work on SQL Source Control lately. We’ve recently improved performance when you link a database, go to the commit and get latest tabs (especially subsequent visits where we can rely on data being cached), and when selecting/deselecting all on the commit and get latest tabs.

    If you are still experiencing performance problems, please make a new suggestion that is very specific to what you would like us to work on. Is it a specific step in the commit process that is taking a long time? Is it viewing history that is taking a long time?

    We’ve also started to work on this suggestion, Don’t refresh the commit/get latest automatically, https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462220-don-t-refresh-the-commit-get-latest-automatically, which will also help with performance.

    Contact support@red-gate.com if you can share your database schema with us for performance testing purposes.

    If you are experiencing problems with server load, please see http://documentation.red-gate.com/display/SOC33/Changing+or+disabling+the+database+polling+interval…

  5. Allow me to add a comment when linking a db to source control

    We have pre-commit hooks enabled in SVN to make sure a reference to a Jira ticket is entered and creating a fresh DB link fails with these enabled as SSC will try to add a standard comment that does not match the required format. Every action requiring an SVN log message, should prompt for one

    3 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…)
    5 comments  ·  Admin →

  6. Simple folder based source control

    Simply output create and alter scripts to a specified folder and its subfolders (e.g. Tables, Views, Stored Procedures, etc.). This would allow any arbitrary source control tool to be used to work with the repository.

    Obviously, the SSMS integration would not be as full-featured, and the user would be responsible for updating, adding, deleting, and committing via their tool of choice.

    21 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  ·  Support Additional Source Control Systems  ·  Admin →
    completed  ·  Gyorgy Pocsi responded

    I’m happy to inform you that the new 2.0 EA now supports simple folder based operation. You can even specify command line operations for each source control operation.

    Please give it a try and let us know your opinion!

    To download the new EA please visit the following link:

    https://www.surveymk.com/s/SqlSourceControl_EapSignup

    You will need to download the VSS/Vault… version.

  7. Failed commit clears comments

    If I attempt to commit something (in this case it was an object with a dependency I didn't include in the list of objects to commit) and that commit fails, you not only refresh the list view again (I can live with that) but you clear the comments. Given the already dismally small field (way too small given how many objects I might be checking in), I have to edit these in a text editor first (you don't support tabs either in there) and paste it in...well, if I don't realize there's going to be a failure (happens often enough),…

    4 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 →

  8. Display History in my time instead of UTC

    It appears the new History feature is using Universal Time Code instead of the local time that is used everywhere else.

    4 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 →

  9. Rebuilding a DB - bug?

    I wanted to test rebuilding my DB from nothing but when I created a new DB with the same name as the old one, SQL source control showed it as already linked (odd but not a problem) but then it told me there were no changes to get and it wanted to commit a drop of everything!

    I worked around it by naming the new DB something different

    1 vote
    Vote

    We're glad you're here

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

  10. Allow For Arbitrary Scripts To Be Checked In to add custom logic for transitions

    It's quite common, when refactoring a set of tables to be able to migrate data from an existing structure into a new structure. This typically happens in 3 steps.

    Create the new structure.

    Migrate the data from the old structure.
    Delete the old structure.

    From what I can tell of SSC, this is not possible.

    36 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…)
    7 comments  ·  Admin →

  11. Clean up WorkingBases After Unlink

    After unlinking a database, I end up with an abandoned workingbase folder. Frequently unlinking/relinking (to emulate an SVN SWITCH between branches) builds up a whole bunch of sizeable folders in workingbase.

    4 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…)
    2 comments  ·  Admin →

  12. It would be nice to be able to have a one click, generate database using the latest verision

    That within the SSMS the ability to generate a create database script off of the repository. I know you can do this in mgmt studio, but being able to have a full script in the repository that will build the database at that version would be sweet.

    3 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…)
    completed  ·  0 comments  ·  Admin →

  13. object level history

    I would like to see history by object. For eg, we should be able to see history for Customer table or Customer.GetOrder sp.

    15 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…)
    5 comments  ·  History/Log  ·  Admin →

  14. Have an option to ignore Extended Properties

    Is there an option to ignore extended properties

    7 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 →
    completed  ·  Chris Smith responded

    SQL Source Control v3.0.5.7 includes a mechanism to allow comparison options to be configured, including ‘Ignore Extended Properties’. To get this version, please run Check For Updates from the Help menu in SQL Source Control.

    Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to configure this option: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521

    Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.

    If you’d like to see an options dialog exposing these settings in SQL Source Control, please vote on the following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.

  15. Copy SQL statement from compare pane

    When I mark an object, I get the differences at the bottom of the window. In one pane is the old and in the other the new sql code.
    I would like to mark and copy this code but the copy functionality isn't available for these two panes.

    3 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…)
    completed  ·  1 comment  ·  Admin →

  16. TFS - Exclusive Checkout / SVN - Lock

    It would be really nice if there was a way to checkout or lock db objects so that I know that I'm the only person working on this object and I will not experience any conflicts when I go to commit the object.

    242 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…)
    35 comments  ·  Admin →
    completed  ·  Gareth Bragg responded

    With SQL Source Control 4.0, we have introduced our new Object Locking feature!

    This feature allows users to lock the SQL object directly on their database server, meaning other users on the same server cannot make changes until you finish you work and release the lock.

  17. Treat renames as renames instead of a drop and an add

    When renaming (tables in this instance) the commit changes dialogue says that there are drops and creations - this will possibly confuse rollbacks etc

    Is it possible for the interface to "understand" renames?

    55 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…)
    9 comments  ·  Admin →

  18. Bazaar VCS

    Can you consider implementing support for Bazaar VCS? Thanks!

    6 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  ·  Support Additional Source Control Systems  ·  Admin →

  19. Allow "Undo" from "Commit Changes" tab

    It would make much more sense to me to be able to look at the Commit Changes tab to see what's been changed and right click on an item and choose undo if I need to revert it.

    4 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 →

  20. Support Perforce!

    49 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…)
    4 comments  ·  Support Additional Source Control Systems  ·  Admin →
1 2 3 5 7 8 9
  • Don't see your idea?