At 02:58 PM 6/23/2003 +1000, Daniel Patterson wrote:
>Greetings all,
>
> I'm looking for advice on the best practises for configuration
> management of stateful data.
>
> This situation comes up in a few different places, but the
> best example (and the one I have right now) are database
> schema changes between software releases.
It is an interesting problem, and one for which I've been unable to find a
clean solution. It would be nice if you could version control the entire
schema. You would also want to version control the data in tables that
provides functionality to the program rather than just data, if you see
what I mean by the distinction.
What I do is version control and tag for release SQL patch files. Each
patch file has a comment at the top indicating the purpose of the change
along with the PR number. That is displayed to the release manager during
deployment, and they can choose whether to run the patch in each
environment, just as a double check that the change is intended to go with
the release.
The upside to this is that it migrates schema changes to each environment
synchronized with the release that depends on them. The downsides are that
it is not easily reversible, and it provides no mechanism to return to the
state at a particular release. I'm still looking for a good answer to that one.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 25 06:37:37 2003