DML automation artifact
vvt
Posts: 1 New member
Hi,
Newbie here, trying to learn the Database Ci/cd. We use the Redgate source control and other products.
We are working on a task to bring our database under version and follow the CI/CD process for the build and deployment.
As part of this,we added a test database to source control. When I add a new object to the DB and commit that to source control, the artifact that TeamCity generates the using DLM plugin includes all the objects. How can configure the build such that I only generate the script of the change?
Newbie here, trying to learn the Database Ci/cd. We use the Redgate source control and other products.
We are working on a task to bring our database under version and follow the CI/CD process for the build and deployment.
As part of this,we added a test database to source control. When I add a new object to the DB and commit that to source control, the artifact that TeamCity generates the using DLM plugin includes all the objects. How can configure the build such that I only generate the script of the change?
Tagged:
Answers
You then need to use SQL Change Automation in whatever deployment tooling you're using (Octopus or Bamboo or ADO etc.) to generate a deployment (or "release") artifact from your build artifact (.Nupkg) which will generate the diff upgrade script plus any drift reports against the target.
It should go:
DB -> VCS -> Build (produces NuGet Package) -> Release Artifact (folder including drift checks and a target deployment sql script) -> Deploy from release artifact
This is because a comparison needs to happen between the accepted (and correctly built) state of the DB from the build which resides in the Nuget, and the target DB you're deploying to.