I would like to ask for suggestions as to the best way to create a patching engine, as suggested by mtherien.
In essence, once a database ( say version_1.0 ) has been deployed to production, any changes to the database from there on out will need to be deployed as patches.
The idea that I have is to create a set of patches for each deployment target, which will be run on deployment. (i.e. run patch_1.1, patch_1.2 etc)
In this way, the upgrade path from version_1.0 to 1.1 and 1.2 can be easily re-created and will provide a repeatable way of testing patches.
I am interested in any ideas anyone might in this regard ?