Deploying Only New Versions Of SQL Objects With Octopus Deploy
Very occasionally we have a requirement where an object is amended in one of the test databases outside of the standard CI process for specific testing due to specific test data being in them. When this happens, those amendments are lost when the CI process runs as it sees the differences and overwrites with the version in the latest NuGet package created from source control.
Does anyone know if there is any way of stopping this behaviour, i.e. if the timestamp on the object (table, proc, function etc.) in the target database is newer than the timestamp in the source control system?
Thanks in advance for any suggestions,