Activity overview
Latest activity by TShiner
Thank you for the quick response! From reviewing the documentation I was coming to the same conclusion. To clarify, this is multiple environments: DEV > TEST > UAT > PROD With only making schema changes the SQL Source Control project has worked fantastically. It's only with a new requirement to run scripts in the database that we have seen this monkey wrench. Two tentative solutions I am looking at are to have the single pre-/post-deployment scripts call external scripts (though that seems too uncertain to work) and to add another task in our deployment pipeline to read all scripts in a directory and execute them (most likely to happen). I have started to review the SQL Change Automation project type as that definitely handles multiple deployment scripts, though when working through a proof of concept it didn't look to keep the full DDL schema in the source code (only what changed since the previous commit / migration script generation), which makes that undesirable. I have not checked out Flyway Desktop, but I will take time to review that too. Thank you for! / comments
Thank you for the quick response! From reviewing the documentation I was coming to the same conclusion. To clarify, this is multiple environments: DEV > TEST > UAT > PRODWith only making schema ...
Is it possible to have multiple pre/post deployment scripts?
My team utilizes SQL Source Control and Azure DevOps Pipelines for deploying database changes throughout our environments. We recently have a scenario where we would like to use pre-deployment scr...