6 results found
An error occurred while saving the commentChad 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
21 votesKendra 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.
4 votesChad Hattabaugh shared this idea ·
6 votes0 comments · SQL Source Control » Better Support for Shared Db Dev Model · Flag idea as inappropriate… · Admin →