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

177 results found

  1. We are only interested in source controling the object definitions. We have a lot of volatile permission changes which we don't want to record, and its actually a hug obstacle constantly having to go in and check off 300 objects to commit just because someone changed a users permissions on them.

    62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    SQL Source Control v3.0.5.7 has been released and allows you to configure comparison options – inlcuding ‘Ignore Permissions’. To get this version, please run Check For Updates from the Help menu in SQL Source Control.

    Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to do this: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521

    Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.

    If you’d like to see an options dialog exposing these settings in SQL Source Control, please vote on the following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.

  2. text area too small- didnt even notice it. Would be good to have multiline comments.

    60 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  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. We need SQL Source Control to comply with the policies in force for the project. eg. Checkin policies, associate with workitem policy.

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    SQL Source Control 3.3 now evaluates TFS policies when committing DB changes. For more information see http://documentation.red-gate.com/display/SOC3/This+commit+doesn%27t+meet+the+server%27s+policy+requirements%2C+or+the+policy+isn%27t+configured+on+your+machine.

    To upgrade, use SQL Source Control’s “Help > Check for Updates…” menu item, or download directly from http://www.red-gate.com/dynamic/products/sql-development/sql-source-control/download.

  4. During the script compare, it would be nice to be able to ignore collation, PK names, FK names, etc...

    I have the same table on two servers, PK for the table is call PKOrderDetails76E0ADF on the other its called PKOrderDetailsAC45C0F.

    Given that its a rather hefty clustered index, I don't particularly want to recreate it just to have the name in sync.

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    SQL Source Control v3.0.5.7 has been released and allows you to configure comparison options – including ‘Ignore Collation’ and ‘Ignore constraint and index names’. To get this version, please run Check For Updates from the Help menu in SQL Source Control.

    Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to do this: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521

    Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.

    If you’d like to see an options dialog exposing these settings in SQL Source Control, please vote on the following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.

  5. When renaming (tables in this instance) the commit changes dialogue says that there are drops and creations - this will possibly confuse rollbacks etc

    Is it possible for the interface to "understand" renames?

    55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  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. I had to uninstall RedGate SQL Toolbelt today, and this involved uninstalling 13 separate products individually. It would be nice if the easy installer could uninstall just as easily.

    (So you aren't disappointed that I uninstalled: I was switching over to the MySQL tools.)

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  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. I can right-click on a database (or item within) in Object Explorer and see a choice labelled "SQL Source Control", but all it does is open the tab in the main area. It would be great if it also had a submenu (like TortoiseSVN does in Windows Explorer) which offered "Update", "Commit", "Show log", "Diff", "Revert", "Delete" and so on. Actually it would be great if the latter actions were offered at all (show log, diff, etc.) because to do them now, I need to jump over to Windows Explorer and use Tortoise.

    50 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    In EA2 (v0.2.1), we added Commit and Get Latest to the Object Explorer right click menu. If you would like other features, please vote/comment on the following (we would need to implement these first before adding them to the right click menu):
    Revert/Undo Pending Change – http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/491513-revert-undo-pending-change
    Show Log/History – http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/471982-tab-for-svn-log-show-history-
    Open DB from Source Control – http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/459952-open-a-database-from-source-control
    Diff/Compare with previous version – http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/491523-diff-or-compare-versions-of-an-object

  8. It takes 5mins to update the latest changes on my insanely fast computer. Although getting the latest changes are OK but registering base and calculating changes take ages! Please improve :)

    50 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  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 49 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. The WorkingBases are saved on disk C:\Documents and Settings...”.
    To save disk space on C:\, we would like the Working Bases on the disque D:\ (we have databases with more than 5000 procs). Is there a setup somewehere ?

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Provide option to filtering based on type of objects just like sql compare and then select all or unselect all option. This will speed up the selection process.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  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. When evaluating schema for changes compared to source controlled versions is would be nice to be able to use the same options available in SQL Compare project options.

    For instance changing a comment on a line already containing a comment isn't detected as a change, additionally format (whitespace) changes are not detected as well.

    While this specific scenario is important to my development process not everyone will need the same scenario supported, but the compare options available in SQL Compare are a great place start allowing users control how changes are detected.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    SQL Source Control v3.0.5.7 includes a mechanism to allow comparison options to be configured. To get this version, please run Check For Updates from the Help menu in SQL Source Control.

    Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to configure this option: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521

    Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.

    If you’d like to see an options dialog exposing these settings in SQL Source Control, please vote on the following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.

  13. I find the "Recent Messages" button on the TortoiseSVN Windows client extremely useful. I really miss this feature on SSC.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  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. Sql Source Control can be made better by adding support for git hooks in the Sql Management Studio Source Control interface.

    Example: Create a pre-commit hook to stop outgoing commits if tsqlt tests do not pass.

    Expected outcome: A commit that fails the pre-commit hook should not be created. This is the behavior of the git command line.

    Current outcome: Sql Source Control does not respect the git hook and bypasses it allowing the commit to be made.

    37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    SQL Source Control 7 has now been released. In this version, SQL Source Control now uses the Git command line for all its Git interactions, which means it will support any Git hooks that have been configured.

    You will need to ensure that you have Git.exe available in your system path – the easiest way to do this if you don’t already have Git installed is to download Git for windows (https://git-scm.com/download/win)

  15. I would like for SQL Source Control to also be supported in Visual Studio so my application developer co-workers who prefer this environment can also use database source control without having to switch to SSMS.

    37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  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. It's quite common, when refactoring a set of tables to be able to migrate data from an existing structure into a new structure. This typically happens in 3 steps.

    Create the new structure.

    Migrate the data from the old structure.
    Delete the old structure.

    From what I can tell of SSC, this is not possible.

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  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. Currently we cannot view history of objects from SSMS using Redgate with Git as repository. I think this is a required feature. Also, we cannot add comments while commiting. Can these two features please be considered to be added in future releases.

    36 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  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Elizabeth Ayer responded

    Viewing Git history and adding comments for commit are now available in SQL Source Control 4.1 and higher. Thanks for your patience!

  18. TFS Preview is TFS on Azure and although I can use the current process to set up using my TFS Preview URL TFS Preview uses Windows Live Credentials to connect, if I put them in the user name/ password boxes the connection fails.

    35 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. ReadyRoll looks great but one of it's downsides is that you have to use Visual Studio. If mostly work gets done using SSMS, then switching to Visual Studio is not a great experience.

    Both ReadyRoll and SQL Source Control use the same comparison engines, they both output objects as files on disk and support migrations.

    To satisfy both worlds (making great experience when using Source Control on SSMS) and have a proper way to automatically update databases from source control files using migrations (like ReadyRoll does), SQL Source control should integrate with ReadyRoll - after each commit, a migration script…

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Kendra responded

    In the past year we have introduced a way to do what you have suggested her, which is a hybrid method of using SQL Source Control with SQL Change Automation (which is ReadyRoll under the new brand).

    In designing the integration, we found that some users wanted each developer to generate migrations as part of their workflow, while others preferred for this to be done in batches, perhaps by a DBA, when preparing a deployment.

    More information on the hybrid workflow is here: https://www.red-gate.com/hub/product-learning/sql-toolbelt/a-hybrid-approach-to-database-devops

    Thanks very much for this suggestion and we would love further feedback on whether the hybrid workflow meets your needs.

  20. I can find no guidance on filter patterns. We have a lot of "temporary" tables which start with an underscore. We've previously used object filters to exclude anything which starts with an underscore. This now excludes all objects in the database, presumably because it's using SQL wildcards. Is the filter syntax SSC uses specified anywhere?

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Gareth Bragg responded

    As of SQL Source Control 3.8.13, filter rules now support the standard T-SQL LIKE syntax for wildcard characters (‘%’, ‘_’, ‘[abc]’, and ‘[^abc]’ – see MSDN for details).

    To include wildcard characters explicitly in a filter, they can be escaped with square brackets.

    ‘Equals’ and ‘Does not equal’ operators will not treat those characters as special wildcard characters.

  • Don't see your idea?