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

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
  1. Prevent user from committing other user's changes

    One of the problems with a shared db model, where all developers work against the same database, is that everyone's changes are listed on the Commit List and any user can commit any other user's changes. It would be nice if an administrator setting could be set that would only allow users to commit their own changes There should be someway to prevent other users from committing your changes.

    76 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Shared Model - multiple instances of the same DB

    Most of our enterprise applications have mutiple instances of the same DB schema. We use the shared model and would like to update al instances once we commit changes on one of them. As a workaround we commit the changes and then hit revert changes on the instances we need to update

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  3. Synchronize Replicated Database Environments // or Possible Workaround such as Filter of Table Columns, contraints, indexes, etc...

    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. 'repl_identity_%'
    3. Filter Index by Name or part of it; E.g. 'MSmerge_%'

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Source Control Standalone instead of SSMS snapin

    Source conrtol should be a standalone app not SSMS addin. When performing get latest or commits, on large environments and slow connections this can easily take 20 minutes during which a click anywhere else in SSMS restarts the get latest/commit process. The logical use of source control being a SSMS addon has been outlived.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Allow "Get Latest" in shared model

    We occasionally restore a copy of production db over our development db. With SCC in place I imagine it will work like this:

    1) Everyone commits dev changes that they care to keep

    2) perform restore

    3) One person relinks SSC in dedicated mode and uses "get latest" to pull down latest schema to the newly restored dev db.

    4) everyone can resume working in shared model.

    To cut out the relink in step 3, it would be nice to be able to use the "Get Latest" tab in shared model for occasions like this

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Connect same database to multiple branches

    We use the shared database development model and can have several projects going at once. Some developers may jump back and forth between projects. It would be nice to have the ability to setup a single database connection to multiple branches. Possibly using the SSMS registered server name instead of the physical server name.

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. SQL Source Control support SQL Server maintenance jobs

    It would be mint* to be able to have SQL Server Maintenance jobs included in SQL Source Control. Could it be added as a new feature?

    * (see kid from Super8 movie)

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  8. Implement the "IGNORE" rules so that database objects can be completed filtered out of source control

    Introduce something similar to the "IGNORE" rules found in your Schema compare for Oracles solution to the SQL Server Source Control product.
    The problem that exists for those of us with third party databases that have 10's of thousands of objects is that they are not workable using this product because it ONLY applies the filter AFTER it has already tried to extract and manage the ENTIRE database. The "IGNORE" option would allow us capabilities similar to filter but they would be applied UP FRONT and BEFORE the system ever tried to gather and manage every single object in the…

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  9. When committing, show when multiple people have edited an object

    When comitting:
    Andy makes an edit and "Changed By" shows "Andy" (but does not yet commit).
    James then makes an edit and "Changed By" is now "James", but does not mention "Andy"

    It would be useful if it could show "Andy, James", to highlight a potential conflict.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Source Control - Changed by unknown

    Problem:
    Sysadmin role is required to see who changed a DB object. I am not permitted to have this role and I would imagine many devs are in the same boat. This means that when many objects have been checked-in by many users it is hard to pick out one’s own changes.
    Solution:
    Have an option when checking-in which adds a 1 line encrypted comment to the start or end of each object script. The comment would contain the username of the person making the check-in (and a control parameter like the time of check-in for instance)
    This username can…

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. On conflict when commiting changes able to right click and open proc/table in new sql editor

    When you get conflict when commiting changes it would be nice to be able to right click and open proc/table in new sql editor, do you change (merge) and continue.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Make SQL Source Control external to SSMS

    Make SQL Source Control external to SSMS like SQL Compare. This would allow the developer to use what ever IDE they want to and still commit the changes the same way. I would use SQL Compare to make changes, but it can't do everything SQL Source Control can. Mainly the migration scripts and the pre and post scripts.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Support Database Projects Referenced as Same Database in SSDT

    Currently, when comparing an SSDT project using SQL Compare, it only loads the base project. If the project references another project as the same database (the standard workaround to the circular reference problem), the objects in the referenced project will not be compared. This can lead to changes being missed and deployments failing.

    It would be nice if SQL Compare could follow the reference back and include the objects from the referenced database in the compare as well.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. SQL Source Control - Filter

    We are a shop that have multiple systems for clients that we managed from within a single database, using a separate Schema for each system.

    I would like to be able to link a TFS database to a filtered list of objects (preferably) an entire schema but I could see where others might like just a subset of other objects.

    If this is currently possible please let me know but I do not see a way to accomplish this without having a separate database for each system per client.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Link source control to Schema, not database

    We couple applications with schemas, not databases. It would be great to link source control to just one schema, rather than the entire database. This way, we can source the code for the application and the database in the same branch

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Use Visual Studio or VS Code as a merge tool.

    Add support for manually merging changes in Visual Studio or VS Code instead of KDiff3 or Beyond Compare

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Fortress - Exclusive Checkout / Object - Lock

    Similar to how fortress works with visual studio. All objects in the database would require an exclusive or shared lock to be worked. If an object is changed without a lock it becomes renegade for that user.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. For shared development environment, replace "GET ALL" with list of historical changes made

    When developing in shared enviroment, I'd love a history tab that I can review all revisions with details, and not have to have a modal window separately. I believe this should be integrated into the main source control tab as change history log. This could help make others aware of changes made that could affect them, yet were already committed. Thanks!

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. compare what I am about to check in against the previous check in

    I see the changes to be checked in , these may have been done by other developers. I want to compare the changes about to be checked in against the previous version to see what changed before I check in.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  20. Create a 'Mixed' model in addition to 'Shared' and 'Dedicated'

    We generally share one database, but occasionally our developers keep a local version. All of these point to source control, which we consider the 'official' version of the database. A developer could commit changes to source control from their dedicated database. They could even edit the code manually.

    However, if we set up the shared database under the 'shared' model, we can't get latest from source control.

    We currently work around it by setting every database as 'dedicated', even the shared database, but then we miss out on keeping track of which users made which modifications.

    Please offer a 'Mixed'…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base