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

587 results found

  1. 10 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. We are unable to use SQL Compare to deploy Migration Scripts to all of our environments and simultaneously maintain commit level control over what does or does not get deployed to each environment for each release, especially with the high volume of changes and the number of last minute changes to release choices in the final stages of release planning. The amount of manual review of the final deployment script is unsustainable.

    Using Powershell, we would like to auto-generate Migration Scripts for each Commit/ChangeSet and Commit those Migration Scripts to TFS. This would allow us to modify the content of…

    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)
  3. It is not possible to resize the columns on the Migrations tab. This makes it difficult knowing which objects to include when creating new migration scripts as most of the names are truncated.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  5. Merge conflicts cannot be resolved if both users commit and one of them pushes.

    To reproduce this behavior:
    1) user A performs a change on a line of a SP
    2) user A commits and pushes
    3) user B performs a change on the same line of the same SP
    4) user B commits
    5) user B tries to pull and a message says conflicts must be resolved outside SQL Source Control and it is also impossible to push (please see the attached screenshots)

    Only if user B performs step 4 after step 5 it is possible to see the…

    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)
  6. It would be really nice if SQL Source Control allowed commit undo like git reset --soft or tracked the filesystem as Git does instead of tracking commits.

    Scenario that highlights this unexpected behavior:
    - perform some changes on the DB
    - commit changes
    - perform a git reset --soft from command line (undoing the commit while keeping changes on the DB and file system is not possible from the SQL Source Control UI)
    - if further changes are performed from the UI it is possible to commit current changes (old + further changes), but if SQL scripts are changed directly,…

    2 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)
  7. 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)
  8. Basically when you compare then you want the script to generate by checking if the database object exists then perform the appropriate action. So, if you are updating a stored procedure then there should be two blocks of statements where the first block is to check if the stored procedure exists and if not exists then create the stored procedure else alter the stored procedure. This should be applied to other database objects such as tables, columns, views, functions, stored procedures, user defined table types, etc.

    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)
  9. When doing a Get Latest in SQL Source Control, if database is registered in DLM, then register the known schema from SQL Source Control

    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)
  10. Have asked for this from support several years ago when the Source Control first was offered. Surprised still no command line interface. The ability to automate saving db changes automatically into TFS or GIT would be widely accepted by the DBA community. I would purchase it tomorrow if was made available.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  12. 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)
  13. We use SourceControl in an MSSQL Merge Replicated database. The database uses ID pools, which generate contrains all the time with new pools for each table.

    The result is that all those tables show very frequently as if they were "changed", while that's technically true we don't care about those changes (those are system generated constrains, we don't want to source control that). It is basically garbage in our "changes" view, and it is actually preventing us from keeping our changes properly committed (hard to look for the changes one is doing, if there are 100 tables changes sitting around).

    53 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)
  14. The SQL Source Control uses the default trace in SQL Server, however this is stored in the tempdb which can be cleared after a restart.

    RedGate suggest using a change log database as shown in the link here: https://documentation.red-gate.com/display/SOC3/Logging+changes+to+shared+databases

    However, this requires you to manually edit the Engine Options xml file in the user profile, this should be configurable in the UI making setup a lot easier. If you have 10 or more developers it requires that those developers maintain their own Engine Options xml file.

    It would be great if this is configurable through the UI on Setup when…

    2 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. With Many databases source controlled. It would be great if there was a function to view changes and updates across all databases. At the moment databases have to be updated one by one. very time consuming

    36 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)
  16. I would like to be able to copy the Filters to different databases, or have a Filter template which I can save to apply to other databases. There are many objects which I do not want to be moved from Development, QA, Integration and Production. Currently, I generated the XML using a query with sys.databases and saved it to DifferenceFilters.xml which is a pain.

    10 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)
  17. I have a single repository for a project that contains both database files and c# code. Currently, git support only allows me to commit database files, leaving the c sharp code out of step and potentially in an inconstant state.

    It would be great if sql source control had the option to stage and commit other changes in the repository (or allow me to generate files but not commit changes - similar to working directory mode).

    9 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)
  18. In the commit window, have a search field as in SQL Compare to locate item to commit

    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)
  19. 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)
  20. Create a way I can synchronize:

    1. NON REPLICATED database X REPLICATED database
    2. REPLICATED database X REPLICATED Database

    Ability to syncronize tables/columns, views, sps, triggers, functions, indexes and constraints.
    Avoid displaying individual constraints used for replication. E.g. Constraints that use range of IDs, Indexes of merging, etc.

    == OR ==

    Allow me to:

    1. Filter Table COLUMNS by Name or part of it; E.g. 'rowguid', '% column name %'
    2. Filter Constraint Name or part of it; E.g. 'replidentity%'
    3. Filter Index by Name or part of it; E.g. 'MSmerge_%'
    61 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)
  • Don't see your idea?