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. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Do not allow to commit changes to an object that is locked

    I don't see why is good this product if it's posible do commit to an object that is locked. If the object is locked this means that the user is editing it Then why allow to commit to this object

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. migration scripts

    When re-linking databases to source control, there is a warning message about loosing all uncommitted migration scripts, with only a OK/Cancel option. It's seems there should be an option for 'take me to the commit page' so that I can commit those scripts, then re-link.

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users

    Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users

    If it is there it will be very much helpful for most of the development projects not testing and production.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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.

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. 4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. When a user closes a session/SSMS it would be useful to have the user to prompted about any pending check-ins (shared db).

    We use a shared environment, and if someone forgets to check something in, then the changes made appear as if from the next user to edit the item.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Syntax-aware comparison of revisions

    Add an option/feature to actually parse the SQL ("Syntax aware") when comparing two different revisions, such that a change in just whitespace understands that the code is the same, even if the file(s) stored in SVN/other source control are different. Some people format things differently if they're not following standards in an org.

    One "simple" way to do this would be the highly-voted option to use the SQL Prompt formatting engine to apply formatting to both revs and then see if there's a difference.

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. support merging with ultracompare

    I would like to see UltraCompare also supported as a Merge Tool.

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. On the "Get Latest" page, provide a way to globally un-check all objects

    Can you please provide a way to "Uncheck" the entire list of objects on the "Get Latest" tab. I have 100+ objects ( Team of 6 Devs ) to get latest and 3 or 4 objects have issues, so I have to manually uncheck each of the 100 checkboxes and then check just the ones I think are ok to check in

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Add filter option for filegroups

    Add an option in the SSC filter to ignore differences in filegroup location as there might be multiple instances of a controlled database that have different filegroup configurations

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Add Filter to Migration Scripts

    Add Filter to Migration Scripts

    When you go to create the migration script, you get to choose which commits are part of that script. It would be great to sort the migration script by the product descriptions or tags. When we have multiple commits to a database, and we might commit #project1 and #project 2 back and forth for a month, and instead of having to ctrl click through every other one, it would be great if we could group them together (or filter) and then generate the migration script easier.

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Customize headers, footers and batch footers in migration script

    I'm hard pressed to think of any corporation that would take a migration script and run "as is". You will at the minimum have some standard code or comment block to put at the top and bottom of a script.

    For example, in our particular place, we check the DB version before running a script (header), and stamp a version on success / error handle (footer).

    We also have special statement which we need to put after each batch (where the migration currently places a "GO").

    Needless to say, having to manually do this is time consuming. So my suggestion…

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base