Skip to content
← Customer Feedback for Redgate

Settings and activity

1 result found

  1. Flag to Force a deployment

    17 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…)
    3 comments  ·  SQL Change Automation  ·  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

    For clarification for readers, this request is specific to SQL Source Control projects which are deployed by SQL Change Automation. Comments in the item give more detail.

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

    I fully agree to this idea.

    We have run in the issue this week, where expected changes to production did not happen due to this issue.

    The post-script is a very usable place to enforce changes to data, for example setting defaults for a new field.

    It is a common mistake that the development team first introduces a new column and forgets to set a migration script in the post-script. After a bug report, the issue is fixed in the post-script. If for some reason, there is no other change, the post script is not applied. More so, since we have 3 environments, dev, tst, prd, the redgate tool should be a trusted help, not something to work arround.

    Since the postscript should be repeatable by nature, this should not be a problem to apply this every time, given it a much more stable transition to production.

    Thanks.