Skip to content

Settings and activity

3 results found

  1. 78 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)
    MCTSQL supported this idea  · 
  2. 153 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  ·  SQL Search  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    MCTSQL supported this idea  · 
  3. 476 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)
    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.

    An error occurred while saving the comment
    MCTSQL commented  · 

    Command line access to SQL Source Control's actions is exactly what I need as well.

    An error occurred while saving the comment
    MCTSQL commented  · 

    Command line access to SQL Source Control's actions is exactly what I need as well.

    An error occurred while saving the comment
    MCTSQL commented  · 

    Command line access to SQL Source Control's actions is exactly what I need as well.

    An error occurred while saving the comment
    MCTSQL commented  · 

    Command line access to SQL Source Control's actions is exactly what I need as well.

    MCTSQL supported this idea  ·