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

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

586 results found

  1. Keeps detecting changes for value s'

    Hello,
    I have a table with only one PK column of type nvarchar(200) which contains static data.
    Source Control keeps telling that there are changes even after saving the changes. It seems that it has some issues with the value s'

    Database version:
    -- Only In Database

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N's''')

    -- Identical

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'a')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan de')

    Latest source control version:
    -- Only In Source Control

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N's''')
    --…

    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…)
    0 comments  ·  Static Data  ·  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. Refresh SQLPrompt after get latest

    After running get latest refresh intellisense and sql prompt cache.

    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…)
    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

  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

    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

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

    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

  5. 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

    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

  6. 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

    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 →
    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. Display summary of Static Data differences

    When displaying the Static Data differences in SQL Source Control it would be very useful to show the number of records that are Different/Identical/In Database Only/In Source Control Only.

    When tables have thousands of records it can be difficult to know the scale of what you’re about to check in or get by just scrolling down a long list. A tab displaying the records for each distinct group would be even better.

    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…)
    0 comments  ·  Static Data  ·  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. Tie multiple task IDs to one commit

    We use SQL Source Control with TFS. It would beneficial if we could tie multiple task IDs to one commit and all changes would in one change set.

    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…)
    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

  9. Bug: Scripts for objects with extended properties full of garbage

    When adding an extended property to any table that contains non-varchar or -nvarchar extended properties, three lines of junk code are added to the bottom of the object script file for each of those extended properties (declaring a variable, setting that variable with a select, and a GO).

    I believe that this may be related to an issue in the Compare engine that I already opened here https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/39729406-more-efficient-scripting-for-non-varchar-nvarchar — it's really beginning to seem like Compare and Source Control aren't usable unless your database modelling follows the pattern that Redgate expects. I don't think it should be that way round…

    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…)
    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. Add an extra input field for referencing work items instead of including #A[item number] in the comment

    Using TFS where a reference to a bug or work-item is enforced as a check-in prerequisite. When typing in a comment, it's easy to forget the #A... rule. especially since TFS has a #[item number] rule without the "A". In adition it is not clear how to refer to multiple items.
    An extra field instead of "comment syntax" would make life easier.

    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…)
    0 comments  ·  Support Additional Source Control Systems  ·  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. Tabular visualization of static data differences between database and repository

    A tabular visualization with the differentiation between "added" (only in database), "changed" (on both sides existing but with different data) and "removed" (only in repository) would help to check the differences and with a possibility to select certain differences which should be committed, it would also be more efficient that different developers can commit only their own changes on a table, which is linked regarding static data.
    In addition a possibility to hide the unchanged columns in the tabular visualization would also be really good.

    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…)
    0 comments  ·  Static Data  ·  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. Changeset History

    I would like to see my full committed change set history SSMS Source Control, with expanding it down to view the objects that got committed. Then see the committed object vs the current database. I don't want to select each object in the database to see what changed per an object. I need to see what change sets contain what objects and compare with the database. I've mocked image up what it should look like.

    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…)
    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

  13. Split database and bind it to multiple repositories

    It would be nice if Source Control can split a database to multiple fragments (based on filters - for example per schema) and setup a repository folder for each fragment.
    The use case: we have many projects which are using always the same core tables and functions (for example notification, settings, user management, ...) and the others are custom specific in custom owned repositories. I want to simplify change tracking and version handling of these core elements and share them in a public repository so each customer can use them. Currently we are updating a core procedure and copy this…

    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…)
    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

  14. Provide ability to delete/drop objects from TFS / DB

    If from Get Latest / Commit changes it is determined that an object shouldn't exist, currently there is no way to drop the object from the db, or delete it from TFS, via the SQL Source Control UI.

    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…)
    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

  15. Bug: drop database and then recreate causes conflicts

    I have a database managed in SVN. On my development machine I deleted it and then recreated it with the same name. RedGate maintained the link to SVN despite the drop (ok, doesn't bother me) but it then marked every object in the database as being in conflict

    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
    AdminRedgate Administrator (Admin, Redgate) responded

    This is a known issue. I’m glad you’re ok that the link to SVN is maintained. The problem is the underlying working folder is out of date.

    WORKAROUND:
    Option 1)
    On the setup tab, unlink the db from source control. If you still want to manage the db in SVN, then relink.

    Option 2)
    Use the Commit or Get Latest tabs to decide if you want to keep the version in your db and commit it or take the version that is in source control. After making a decision using the radio buttons in the differences pane at the bottom of these tabs, you must then click the Commit and/or Get Latest buttons to actually perform the action.

    HINT: You can select multiple rows by selecting 1 row and then hitting Ctrl-A or select the top row and then hold the shift key down and select the…

  16. Link to TortoiseSVN Repo Browser

    Can we have a link to TortoiseSVN so we can review the repository from SSMS please?

    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

  17. 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

  18. 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

  19. 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

  20. 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
1 2 … 20 22 24 … 29 30
  • Don't see your idea?