2 results found
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.
An error occurred while saving the commentMatt @ Evolve Software commented
We are actually taking a client away from the scenario you describe (backup + restore), as the issues they face are not having any visibility of changes to datasets for integration / acceptance testing - coupled with the fact this is across a number of different countries where the static data is different too.
The focus for our client is to get everything under source control - if it's not under source control then it doesn't exist. Having their seed script for an environment + country combination now gives them a greater understanding of how this dataset has changed. Being able to manage this from within SQL Source Control would just be a value add.
We currently create the db from the package and then have a subsequent step in OD to seed the data using a script from the same package - using the conventions that OD gives us in the form of the Country and Environment we are deploying to.