Skip to content
← Customer Feedback for Redgate

Settings and activity

4 results found

  1. PackageVersion SQLCMD var should be set in PackageScript.sql when calling Export-DatabaseBuildArtifact

    1 vote
    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 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
    Anonymous shared this idea  · 

  2. As an deployment engineer I'd like to run environment specific scripts during deployment

    21 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…)
    2 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
    Kendra responded

    Thanks for this feedback.

    We have quite strong support for this request in SQL Change Automation projects, which support multiple pre- and post- deployment scripts and which also have an option to “seed data” for larger tables which you would like to populate: https://documentation.red-gate.com/sca/developing-databases/concepts/data-population/strategies-for-data-population

    For SQL Source Control, we now support pre- and post- deployment scripts, however you are limited to only one of each type. Additionally, the seed data methodology is not available in SQL Source Control.

    Anonymous supported this idea  · 

  3. Rollback deployments

    20 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…)
    4 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
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    I currently manually create a rollback folder in the project. Then,I create a subfolder nabbed the same as the migration subfolder (e.g 1.1.0-changes). Then, when I import, I copy the revert sql into a rollback script and modify as necessary. Then I import the migration. Then I copy the migration script filename over the rollback script filename and add "-ROLLBACK.sql" to the name.

    I made a powershell script to copy all of the rollbacks for a given folder into a single script in reverse order.

    I'd love to see this more automated in SCA. :)

  4. Offer environment variable as a Build Package Version Number source

    4 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 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
    Anonymous supported this idea  ·