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

588 results found

  1. Where login information is stored for SQl Source Control 3? If A user is using B users SVN credentials and later on A user get its own SVN credentials. How user A can force SVN to ask his own credentials?

    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)
  2. After the list of change to be committed get refreshed, every item get checked by default, even those I just unchecked. Is it possible to not check the item if it was already in in the list and unchecked, or just mark them all as uncheck by default instead of being checked.

    The issue is when I have item that I don't want to commit right now (unstable, unfinished view, etc), I have to uncheck them EVERY time the list is refreshed, which is, every often since the list refresh each time you click on a new object in SSMS.…

    13 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. A table is under source control and the data of that table is linked as static data.
    Both table definition and data has been changed and are visible in the 'Commit changes' tab.
    Since the data is just edited and changed for development purpose it should not be committed.
    But in this situation it is impossible to only commit de table definition.
    When checking the table the data is also checked (and the other way around also).

    It would be nice to be able to commit the changes separetly.

    20 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  ·  Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    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)
  5. Disable Foreig Keys of table of transaction

    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  ·  Static Data  ·  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. Currently RedGate includes these lines to every stored procedure it puts into SVC:
    "SET QUOTEDIDENTIFIER ON" and the "SET ANSINULLS ON"
    Actually I don't think it makes much sense because these are simply db properties and should be tracked and version controlled as a separate database properties script, but not included into every stored procedure file.
    OR it would be nice if we simply can turn it off.

    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)
  7. The source control system keeps thinking a certain table wasn't committed, and marks it up as "changed" to be committed. Here's the table:

    -- Columns

    CREATE TABLE [dbo].[EvaluacionesCiclosEducativosGruposAcademicos]
    (
    [CicloEducativoId] [int] NOT NULL,
    [EvaluacionId] [int] NOT NULL,
    [Grupo] [int] NOT NULL,
    [ProfesorId] [int] NOT NULL,
    [CursoId] [int] NOT NULL
    ) ON [PRIMARY]
    GO

    It doesn't seem to detect this line, and decides it has to insert it again:

    DISABLE TRIGGER [dbo].[tD_EvaluacionesCicloEducativosGruposAcademicos] ON [dbo].[EvaluacionesCiclosEducativosGruposAcademicos]
    GO

    At the time of this writing, it has inserted the very same section 4 times, one after the other, and wants to keep doing it.

    3 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)
  8. When creating the migration script if the developer goes through "cherry-picking" the commit(s) that they wish to include in the migration script. It appears that non-selected commits that are between the selected ones are being picked up.
    For example if the developer chooses commit 1 and 3 and skips 2 the objects in commit 2 are still showing in the migration script.

    I would like to point out that this appears to be a bug and not a feature request, but i am still using 3 votes...

    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  ·  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. Bug: when creating a migration script for a table change that requires dropping Foreign Keys on other tables to this table, the generated migration script does not include the extended properties for the Foreign Keys on the other tables when rebuilding the Foreign Keys.

    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. After creating the database, I added to the shared database model and commited the objects to the repository, but the spinning wheel is not gone and it looks like it is busy or just unable to reset the icon. Even after I disconnect from the database server in my SSMS, my cursor still has the spinning wheel on it. Looks like a bug and it is really annoying and confuses the hell out of users about the status of Source Control process.

    5 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. I would like a way for SQL Source control to leverage TFS work item status and facilitate automated deployment similar to lab management.

    13 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)
  12. When we hop back in our source control repository to an older release and "update" our database, occasionally there is new static data that is referenced by non-static entries in the database. We do not have cascading deletes enabled for various reasons outside of the developers control, but in this particular instance it causes errors when static data is removed from the database to revert to an older version. Would it be possible to have redgate check incoming foreign keys and generate all the necessary deletes to allow static data removal?

    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  ·  Static Data  ·  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. Suggest that the SSCv3 installer NUKE all prior version Log folders e.g., SSCv2 and SSCv1, please...(or at least offer us the choice to have them nuked...) Had Stuart not posted (at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2526239-log-files), I'd have those two folders around for ever...

    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  ·  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)
  14. I often have to put together a changelist that essentially lists the affected objects (tables, SPs, etc.) for documentation purposes. In Tortoise, I can highlight one or more revisions then in a separate page, shift or control select several or all items and hit Control-C to copy that as text. Then I can paste it and get a nice long list of table names, SP names etc like this:

    SomeTable
    AnotherTabl
    uspmyStoredProc
    usp
    SomeoneElsesSP

    It's something I use for documentation and it just would make life so much easier. Not sure if it's a big deal to make that…

    10 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  ·  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)
  15. Do not use transactions but use bulk insert in order to reduce the get latest time. A 'flush and refill' approach using bulk insert should be faster in hours with 10K plus records.

    A two processor, dual core computer with 8GB of RAM and a Windows experience index of 6.5 takes over 8 hours to get lates on 50K records.

    10 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  ·  Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Kendra responded

    Thanks for this feedback and for the votes for this suggestion.

    For users who need to manage larger volumes of static data, we currently recommend versioning the database with SQL Change Automation. SQL Change Automation has stronger support for static data:

    • Supports column filtered static data tables in the SCA plugin in SSMS
    • Supports multiple post-deployment scripts, in case there is a preference to manage static data tables in dedicated post-deployment scripts
    • Allows approaches like bulk loading larger static data tables by supporting SQLCMD variables in migration and post-deployment scripts

    I do understand that you are looking for this feature in SQL Source Control, but wanted to surface this option for other readers who may be interested in either tool.

  16. With a team of 6 using source control, we are finding the performance of both SSMS on individual machines and our developement SQL box to be crippled by Source control.

    Our developement server is showing literally hundreds of connections to TempDB from Sql source Control which is slowing the box considerably

    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)
  17. In our development model we set up a branch for each release of our product in our SCM tool.

    So we need to frequently change the linkage for a DB to the new branch in source control after each release.

    The tool currently doesn't have any edit capability on the linkage, so we are forced to remove and re-add it each time. This is somewhat awkward. Can we get an edit database link feature on the setup tab?

    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. I am suprised there is no SQL CE product considering the knowledge and skillset at this company. I think your prices are a little steep but I would pay a premium for a SQL CE Product providing it did the obvious. Just a suggestion and opinion. Nice existing products though.

    6 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)
  19. We're using CA's SCM for our source control. Would be nice if SQL Source Control could add support for it.

    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)
  20. We have a lot of databases. It's very time consuming to link all databases one at a time for every developer. It should be possible to make use of a solution file to link a solution with all the databases, rather then mapping one by one.

    25 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?