Ability to perform the pre-deployment check separately from the deployment
New-DatabaseUpdate command makes a database update which can take a database from version X to version Y. When you use SQL Release to deploy this database update to a target database, it does a pre-schema check.
Between making of the database update and applying it, the database could have drifted from version X. The check ensures that the target database is actually in version X.
This feature will give you an ability to run the pre-schema check separately from deploying of the update.
Anonymous
shared this idea
Thanks for this suggestion.
This suggestion can now be handled with the ‘Drift’ features in SQL Change Automation 4. It is possible to, just prior to deploying a release artifact, quickly re-rerun the generation of a release artifact simply for the purposes of checking for any new drift, and canceling the deployment if any new drift has occurred.
More info is here: https://documentation.red-gate.com/sca4/reference/powershell-cmdlets/new-databasereleaseartifact