Settings and activity

  1. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  DLM Dashboard  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Chad Hattabaugh commented  · 

    It would be nice if the same workflow could be used for changes made via SSC. If I check something in from Development, Acknowledge the change as being checked in (maybe Changeset id and user who committed? )

    Without an automated workflow around SQLCI, SQLRelease, and SSC this tool just becomes "additional work" as part of a release with little value to the business

    Chad Hattabaugh supported this idea  · 
  2. 99 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  DLM Dashboard  ·  Flag idea as inappropriate…  ·  Admin →
    Chad Hattabaugh supported this idea  · 
  3. 158 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  DLM Dashboard » Version Control  ·  Flag idea as inappropriate…  ·  Admin →
    Chad Hattabaugh supported this idea  · 
  4. 21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SQL Change Automation  ·  Flag idea as inappropriate…  ·  Admin →
    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.

    Chad Hattabaugh supported this idea  · 
  5. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Source Control  ·  Flag idea as inappropriate…  ·  Admin →
    Chad Hattabaugh shared this idea  · 
  6. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)