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. 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)
  2. It takes a while to setup all the exclude filters, and this time is worse when the solution to a problem is to unlink and relink. Provide a way to quickly exclude tSQLt content and/or save / restore filters.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 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)
  3. SourceGear Vault 7.0 is out and now SQL Source Control no longer works. "Server edition is correct, but the version is wrong."

    20 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. When other instances of SSMS are closed, Source Control should be re-enabled.

    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)
    completed  ·  fiona.gazeley responded

    In the Global Options you can choose to allow SQL Source Control to be open in multiple Management Studio windows

  5. Please add support for the current version of svn (1.8)

    27 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. In the "Link to source control" screen there are a number of options.

    We use branches, so our working folder is always the most relevant to what we are doing.

    When we point the link to the WorkingFolder, everything is great, however, the "Migrations" tab is not available for this type of connection.

    This is a pity, because we need to create a migration script that will update the main trunk, when we merge our branch back in.

    Please enable the Migrations feature for the "Workingfolder" type of link.

    3 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  ·  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)
    completed  ·  Elizabeth Ayer responded

    I am delighted to let you know that this is now released! You can now create migrations scripts even when you’re using working folders.

    If you don’t have SQL Source Control installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.

    If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.

    You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples

    Thank you for sticking with us while we worked on this, and please keep the feedback coming!

  7. I have a table called My_Table.

    I should be able to just type "mytab" and have Sql prompt recognize that as an option in intellisense, like devart SQL Complete does. Currently, it gives me no suggestions.

    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  ·  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)
  8. We use Code Collaborator to peer review our SQL code before we submit to our version control (Perforce). This is typically done using a pending changelist, which is probably specific to Perforce. However, it would be sufficient to merely have SQL Source checkout and update the files in the working directory before/without committing.

    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  ·  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 SQL Source Control v3.4, there is an option to link to a working folder. If you use this option, on the commit tab, you can “save” your changes to the working folder. This scripts out the objects to files. You can then use your own tool to review the changes and add them to the changelist and commit them using your own source control system’s client tool.

  9. I am working on a project that is an enhancement to an existing database that is controlled by an external party. I am referencing objects that I have no control over via foreign keys, presently I cannot commit the foreign keys to source control unless I also commit the dependent objects. I do not want to commit these as I do not control them.

    Would it be possible to have some mechanism that permits me to commit my changes without the dependencies, something like an override checkbox for the default behavior that will also place messages in the notification box…

    27 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  ·  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  ·  James Billings responded

    The latest frequent-update version of SQL Source Control (4.0.6.179) allows you to default the checkbox behaviour to off. To do this, you’ll need to edit your UI Options file (RedGate_SQLSourceControl_CommonUI_UIOptions.xml) which you’ll find in localappdata\Red Gate\SQL Source Control 4 and add a tag called IncludeDependenciesCheckbox, like this:

    <IncludeDependenciesCheckbox>False</IncludeDependenciesCheckbox>

    If the value is false, then the checkbox will be un-set by default.
  10. According to Red Gate support, migration scripts only run when using SQL Compare, not when using Get Latest within SQL Source Control. Therefore if I have data, real or test, in every development instance, the Get Latest tab is useless in the product and I must use SQL Compare to deploy the changes. I can't imagine it would be too difficult to just run the migration script when using Get Latest.

    3 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)

    Migration scripts are used in SQL Source Control when Getting Latest. Once you click on the “Get Latest” button, you should recieve a warning about the migration script. If it fails, there will be an option to edit the script it was trying to run. The best thing to do is review the script and execute it in SSMS. If there’s an error, it may be a syntax error within the migration script. Once it is corrected, you can execute the script, then refresh the Get Latest tab and you should be in synch.

    I’m sorry about the confusion.

  11. We already have our database in SVN, is there a way to access that repository?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  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)
  12. Provide a way to link a change during commit to defect in TFS and show it in the history window

    2 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  ·  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)
  13. This is a bug:
    We recently upgraded source control from 1.x to 3.x.; with the new version the icon that indicates there are changes to commit keeps coming up within minutes after actually doing a commit - and on objects that have NOT undergone a structural change. What's going on? Please fix this.

    17 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)
  14. I'm missing an option to add credentials to TFS. Is it not there?

    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  ·  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)
  15. Currently Source Control information is stored in database extended properties in the database being source controled. This requires Alter Database. In production those of us who use RedGate for Source Control, do NOT have Alter database because only the sys admins have that. And they do not want to bother with RedGate as they are just acting as auditors not database developers in production. Other environments we have full rights, just not production. It would be great to have an option to store the "Version", "Linked to" and "Migration folder" in a file not in Extended properties in the database.

    16 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  ·  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)

    Sorry that this has taken so long to deal with, but I’m pleased to say that the latest version of the migrations feature no longer requires extended properties on your database.

    This means that as of version 5.1.1 of SQL Source Control, Alter Database permissions are no longer required.

    Mike Upton
    Technical Lead | SQL Source Control

  16. Allow SQL Source Control to work on SSMS 2012, where SSMS 2008 and 2012 are both installed on the same machine

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 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)
  17. 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.

  18. Support Vault Server version 6.0 that came out recently. Currently when trying to connect against that version, SSC responds with an error of "unsupported server version". It would be nice to make SSC 3.x work with Vault 6.x.

    11 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. On the Get Latest and Commit Changes tabs, user selections do not persist. Every time the window refreshes (which is any time you leave and come back) you lose the selection. Seems odd to me that I would have to request such a feature, as it would seem like the natural way of doing things. If I have hunders of objects to get latest or check-in and i'm carefully selecting, i can easily lose my selection which causes lots of pain :)

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 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  ·  Anna Hall responded

    SQL Source Control version 3.2.0.27 now has persistent user selections (still just on the Commit tab).

  20. Sequence object not yet recognized by SQL Source Control.

    14 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  ·  Better Support for Shared Db Dev Model  ·  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)
  • Don't see your idea?