Combining SQL Source Control with SQL Change Automation
I am looking into using SQL Source Control to manage our database schema changes.
In the future we would also like to use SQL Change Automation as we would like to be able to build the database as a Nuget package in our CI and use the Nuget package to deploy the changes.
After evaluating both for a while it seems like we would need to follow a workflow like this to use both:
1. Make changes on the dev DB using SQL Source Control and commit them
2. Then separately generate migration script in SQL Change Automation project and commit and push them
3. CI builds Nuget package which is then deployed
The above approach is a bit cumbersome so I am wondering is, if there is a better way to somehow use the two tools together? As said above we would like to use Nuget packages to deploy DB changes.
0 · Share on Twitter