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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

588 results found

  1. It would be more than a 'nice-to-have' if we could specifically select and label versions as a "Release". The current assumption is that selecting a specific revision is equivalent, but there are scenarios where it is necessary to keep release a build that spans "revisions" - especially when working on an incremental set of changes.
    The only way I can see to do this right now is to restore all relevant versions individually and then use SQL Compare to manually revert those changes that have been committed in the "current" build but which wee do not want to release yet…

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. I have a bunch of Ruby services which talk to sql server. I'd love to be able to stand up and tear down databases for development using Microsoft's mssql-server-linux docker container while still managing my database via Redgate. This would require a linux-based CLI tool that could create the database from source.

    To do this would require a linux-compatible container

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  3. Add a button to "Unlink, Delete my cache, Relink" so when support asks you to perform that function, it just takes the user 1 step.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Currently there is an option to edit migration scripts however edits will not get applied to other environments if the old version of the script was already run.

    Imagine the scenario where a migration script is created to update one record in a table that does not have it's data versioned. The script is checked in and deployed to the CI environment and the QA (test) environment. QA test finds that the update was incorrect. Development edits the migration script to correct it. The edited script will not get run again on those environments.

    Currently there are only two work…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Using the latest verrsion I cannot create a migration script for selected changes (checkins in the versioning control system).
    The menu option it had in the database context menu is missing.
    Why did you remove this feature?
    It was nice for allowing migrating environments that you cannot connect to.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. From the commit dialog I can see the changes that have occurred and decide whether to commit or not. Then after committing I could generate a script covering those amendments. It appears that you have removed this functionality. Now under Migrations I just get a list of objects with changes and have no idea what has changed and just have to blindly generate a migration script or flick back and forth between the Commit tab and Migrations tab to determine what to include.
    Maybe I have missed something - only been trying for a day!

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  7. In the commit tab you can see the differences between source control and the database which makes it great for deciding what you want to commit or rollback. If you select items in this tab and them right click and undo changes your selections are lost and you have to re-select in the Undo Changes dialog which doesn't let you see the change.

    As a developer I want to be able to see the change that I am about to undo.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. When committing changes it would be nice to be able to mark changed items as "Covered / Included in existing migration script" so that they are not checked into source control. I am specifically talking about uncommitted schema changes. For example, transferring a table to a different schema. SQL Source Control sees this as a drop (from old schema) and create (in new schema), but there are times when it should be an ALTER SCHEMA statement in order not to lose the data from the table. The ALTER SCHEMA can be added to an existing migration script instead of creating…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. On one of our databases we have a lot of changes we don't want to commit at the moment, it would be great to have UI filter on commit tab so we can easily find one of the changed procedures/tables/functions by schema/name and select it for committing.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. If I exclude items from source control they should not default to be committed due to dependencies. It would be great if there was a setting when items are excluded to never include them in the list of items that are dependencies.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. If you have a HiDPI or 4K display, SSMS is scaled to 2x. In SQL Source Control, The Commit and Get Latest tabs are fine, but the Migrations, Locking and Setup UI are scaled MUCH larger than 2x. I would prefer those UIs be scaled to 2x.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. I would like to be able to pause/start scanning a database for changes as will. It is trying to do several at the same time right now and one of them is huge which is taking longer than it should. If I could only scan the one I am working with at the moment it would save me time system resources.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  13. Add option like SQL Search application for quick acces to object

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Sometimes I'm connected to multiple instances and it would be nice if the Source Control tab made it clear which instance I was about to change or commit from.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. This more a bug report than a feature suggestion. When i start Microsoft SQL Server Management Studio 10.50.2500.0 the fontsize is fine. But as soon as redgate loads the font size are changed.
    See here: https://stackoverflow.com/questions/40207918

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  16. The open in excel feature is impressive and I love to use it for ad-hoc extracts. Having the ability to extract multiple results in 1 go to a single Excel file with different sheets would be great.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  17. This filter should exclude an object with a schema that has a matching name.

    -- All Objects

    Exclude where (@SCHEMA = 'tSQLt') OR (@SCHEMA = 'SQLCop')

    Did not exclude this schema object definition.

    -- Schema

    CREATE SCHEMA [tSQLt]
    AUTHORIZATION [dbo]
    GO

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  19. When linking static data to source control the unicode characters are appearing as question marks
    so please add the support for the unicode characters in the script files

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  20. The blue circle indicating changes to be commited should auto-refresh (added/removed when necessary) and refresh when the SQL Server refresh icon or menuitem are clicked.

    Now it only refreshes when the user goes on the Commit or GetLatest tab.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 6 8 10 29 30
  • Don't see your idea?