Skip to content
← Customer Feedback for Redgate

Settings and activity

3 results found

  1. Database Diagrams

    156 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…)
    7 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
    Pouya Yousefi supported this idea  · 

  2. Need ability to suppress conflicts about constraint name changes.

    9 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…)
    0 comments  ·  SQL Source Control » 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)
    Close
    Close
    AdminRedgate Administrator (Admin, Redgate) responded

    SQL Source Control’s Get Latest should be used in a dedicated model to update your different dev machines. This would keep the constraint names consistent in your dev environment.

    You can use SQL Compare to deploy changes to other environments. SQL Compare has an option to ignore constraint and index names so that these differences won’t appear.

    Pouya Yousefi supported this idea  · 

  3. Change branches from SSMS.

    207 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…)
    under review  ·  21 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
    An error occurred while saving the comment
    Pouya Yousefi commented  · 

    Thanks @David. My team has been pivotal in getting that moved up to where it is and we are anxiously awaiting its implementation.

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

    My local mercurial repo is pointing to the default branch. I have database changes that I need to commit but I want them to go to a new branch. There is no way from the SQL Source Control commit window to indicate that I want to create and commit to a new branch. Currently, I have to make a bogus change in my local SQL repository directory and commit that to a named branch in order to set my location and then commit using SQL Source Control.