Skip to content
← Customer Feedback for Redgate

Settings and activity

1 result found

  1. Command line tool (or API) for SQL Source Control Integration

    476 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    64 comments  ·  SQL Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    under review  ·  Kendra responded

    Thank you everyone for the suggestions and votes for this over the years.

    I’d like to surface up a workaround for the “linking” problem which is mentioned in the comments. For the use case of easing pains around environment setup with a large number of databases, we have had customers find success using code based off Alessandro Alpi’s blog post: https://alessandroalpi.blog/2016/06/28/automatically-link-databases-to-red-gate-sql-source-control/

    I do understand that this is a broader issue and hear that many of you also want command line or API support for the product in general.

    If there are specific scenarios or workflows that would be useful to automate for you, this feedback is also very useful, and if you have details on the type of VCS you use and the workflow (such as a branching model) that it would fit in to, that would be very helpful for us to hear as well.

    Joe supported this idea  · 
    An error occurred while saving the comment
    Joe commented  · 

    +1 On this feature.

    I currently work on a database-intensive software project. We currently work with 8+ developers on a single development environment, which contains 3 database instances containing 40+ databases in total. There is only one development environment and developers have no local workspace/database instance.

    Manually relinking/updating each of these databases (for example linking to a newly created branch or when you want to bugfix in a previous release) would take too much time if this has to be done manually.

    I know this is not the ideal development setup, but that is not the issue we wish to tackle first.

    I like the appeal of SSMS source control integration and automatic change script generation that other tools lack, but the manual intervention required is just too big a problem to seriously think about SQL SC.