4 results found
1 voteAnonymous shared this idea ·
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.
Our current guidance for rollback support on SQL Change Automation is here: https://documentation.red-gate.com/sca/developing-databases/concepts/advanced-concepts/rollbacks
Our roadmap for 2021 does include further researching and evolving rollback procedures: https://www.red-gate.com/products/redgate-deploy/roadmap
An error occurred while saving the commentAnonymous 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. :)