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. High DPI screen scaling doesn't work well with SSMS 2016 RC3

    High DPI screen scaling doesn't work well with SSMS 2016 RC3.
    The source control screen doesn't fill the entire work area, but just takes up a small rectangle in the top left (approximately 50% x 50% of the work area).
    This occurs on a 3840x2160 pixel screen, SSMS version 13.0.14000.36, red gate source control version4.4.0.1714 standard

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

  2. Either needs to support x64 assemblies or have the ability to ignore them

    17 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. Source Control bug: Changes to Commit icon

    This is a bug:
    We recently upgraded source control from 1.x to 3.x.; with the new version the icon that indicates there are changes to commit keeps coming up within minutes after actually doing a commit - and on objects that have NOT undergone a structural change. What's going on? Please fix this.

    17 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 →
    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. Option to store the "Version", "Linked to" and "Migration folder" in a file not the database

    Currently Source Control information is stored in database extended properties in the database being source controled. This requires Alter Database. In production those of us who use RedGate for Source Control, do NOT have Alter database because only the sys admins have that. And they do not want to bother with RedGate as they are just acting as auditors not database developers in production. Other environments we have full rights, just not production. It would be great to have an option to store the "Version", "Linked to" and "Migration folder" in a file not in Extended properties in the database.

    16 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
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    Sorry that this has taken so long to deal with, but I’m pleased to say that the latest version of the migrations feature no longer requires extended properties on your database.

    This means that as of version 5.1.1 of SQL Source Control, Alter Database permissions are no longer required.

    Mike Upton
    Technical Lead | SQL Source Control

  5. Stop offering upgrades as if they were updates.

    You software goes out and looks for a update every time it's started and then pops up a little notice. When I clicked on this thinking I was getting an update to my existing software, it installed a new trial version and uninstalled my older licensed version. This is not only irritating, I think it is underhanded and reprehensible.

    16 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 →
    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
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    The new update mechanism (the blue bar at the top of the screen) should make it much clearer when your support & upgrades status means you’re not entitled to a major version upgrade, and therefore upgrading would start a new trial instead.

  6. 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 →
    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. Require lesser SQL Server permissions than dbo to use

    The permission of dbo required to use SQL Source control is not good and indeed a lot of dba's do not like the idea of having to grant dbo permission for users who wish to use the source control. In some companies it would not be possible to grant dbo permission.
    Could SQL Source Control be changed to not require dbo but perhaps something lesser. Indeed give the option to not writes extended properties at the database level.

    14 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 →
    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
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    I’m pleased to say that the latest version of the migrations feature no longer requires extended properties on your database.

    This means that as of version 5.1.1 of SQL Source Control, Alter Database/dbo permissions are no longer required.

    Mike Upton
    Technical Lead | SQL Source Control

  8. Choose when to calculate static data changes

    Our static data tables can have a few thousand rows each. It's costly to have the rows compared every time the SQL Source Control tab is opened to push/pull schema changes (which are much faster to compute). Can the schema and data aspects of this tool be separated to prevent excessive comparisons on data that by nature changes very infrequently.

    14 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  ·  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

  9. Support for SEQUENCE object

    Sequence object not yet recognized by SQL Source Control.

    14 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  ·  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

  10. Works very intuitively

    Adding a database to a repository and doing the first commits works very intuitively. Great job!

    14 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

  11. Commit single changes

    I like the ability to right click on a single item and select commit to source control. However, when doing this SQL Source control calculates all of the changes in the database. Can the behavior be changed here to only show the changes for the object selected to commit?

    Thanks

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

    Even though we calculate all the changes, only the object you right-clicked on should be checked. (It should also be scrolled into view, if you have a long list.) Therefore, you can commit just this 1 object.

  12. Stop treating Git like a red-headed step child.

    GIT seems to always get the short end of the stick. Can't do Object Locking, can't do Migrations, can't do Get Latest, can't View History.

    Please stop treating GIT like the middle child in the Brady Bunch. GIT is totally Marsha, not Jan.

    13 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 →
    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
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    I love your request to much, I’m going to hate to close it as finished soon….

    Git is a first-class citizen in SQL Source Control 4.1, which is scheduled to go out within a couple of weeks. You can get it right now if you sign up to the ‘Frequent Updates Channel’ (instructions here: https://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates).

    We’ve added Commit, History, Push and Pull (Pull+Apply changes = Get Latest) for Git.

    Object locking can be used with Git, but it’s a database-level thing, so is really only useful if you have multiple people sharing a database – a relatively uncommon set-up for Git users.

    The latest version of Migrations, in SQL Source Control 5, now supports all version control systems, including Git.

    Since that covers every item on your list, I’ll mark this as completed – but thanks for making us giggle too.

    Mike Upton
    Technical Lead | SQL Source Control

  13. View "Get Latest" script before execution

    It would be beneficial to see the sql script that "get Latest" finally executes (with the option to execute having screen the scirpt) . I have found this very useful in other db sync tools especially if the script fails.

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

    You could use SQL Compare Pro and the SSMS Integration Pack to see the script.

    If the script fails, then you will have the option to view the script in a query window and you can edit it as needed.

  14. Support SQL Server Management Studio 2012

    Allow SQL Source Control to work on SSMS 2012, where SSMS 2008 and 2012 are both installed on the same machine

    12 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  ·  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

  15. Problem syncing Service Broker items

    Have two service broker services that won't synchronise.

    Database version shows,
    CREATE SERVICE [//DBA/Login-Service]
    AUTHORIZATION [dbo]
    ON QUEUE [dbo].[Login-Queue]
    (
    [http://schemas.microsoft.com/SQL/Notifications/PostEventNotification]
    )
    GO

    Source control version shows,
    CREATE SERVICE [//DBA/Login-Service]
    AUTHORIZATION [dbo]
    ON QUEUE [dbo].[Login-Queue]
    GO

    When I try and commit the changes, it stops at the "Sending Files ..." step and says "Nothing to commit"

    11 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

  16. Faster way to exclude all tSQLt content

    It takes a while to setup all the exclude filters, and this time is worse when the solution to a problem is to unlink and relink. Provide a way to quickly exclude tSQLt content and/or save / restore filters.

    11 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  ·  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. Stand-alone app

    I'd suggest rebuilding Red Gate SQL Source Control into a stand-alone application (similar to SQL Compare & SQL Data Compare), instead of a plug-in to SSMS.
    My SSMS has gotten awfully slow since installing SQL Source Control, even after unchecking the Changed Object & Static Data control options, AND setting EnableObjectLocking to FALSE under the hood.

    Consider that I'm working all day in SSMS, but I only need SQL Source Control maximum once or twice a day, when committing changes to Git.

    Kind regards,
    Christof

    11 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

  18. Vault 6

    Support Vault Server version 6.0 that came out recently. Currently when trying to connect against that version, SSC responds with an error of "unsupported server version". It would be nice to make SSC 3.x work with Vault 6.x.

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

  19. Support for Source Gear Fortress (Vault Professional Edition)

    We moved source control to a product by Source Gear called Fortress. Great Source Control. I would like Red Gate to support this.

    11 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  ·  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

  20. Don't show conflicts when working in a Shared (Centralized) DB Model

    In a dedicated db model, a conflict will occur when User1 and User2 both make a change to Table1. User1 commits the change successfully. When User2 tries to commit, they will be notified of the conflict. User2 must then decide if they want to take what's in source control or keep their version and commit this to source control. In either case, User2 may need to reapply some changes to the db and re-commit.

    In a centralized db model, when all developers are working against the same db, these conflicts should NOT occur.

    10 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  ·  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
1 2 4 6 7 8 9
  • Don't see your idea?