Re: Schema Upgrade

From: Christopher M. Day <christopher.day_at_rdbms.freeserve.co.uk>
Date: Fri, 11 Jun 1999 09:43:33 +0100
Message-ID: <3760CC35.75B09F35_at_rdbms.freeserve.co.uk>


Bhavesh,

I had a similar problem on my last contract, the most cost effective solution was to buy Quest software's Schema Manager. Might be worth getting it on evaluation just to see what it does ;) http://www.quests.com

Chris.

"Bhavesh A. Doshi" wrote:
>
> Hi,
>
> I am working on a problem on schema upgrade and needed some information on
> it.
>
> In a database system which has many database accounts with the same
> schema, in time, one would need to change the schem which could mean that
> new columns are added or deleted or moved to different tables,
> computations
> may need to take place to populate newly introduced tables or columns, and
> table merges to support normalization or table divisions, index additions,
> etc.
>
> How does one go about upgrading the schema in an efficient manner and also
> have the current schema laid out in one place for a developer's reference
> and future upgrades ?
>
> One approach is to maintain two master copies: One being the complete,
> homogenized schema and the other a serial collection of upgrade
> procedures. But these two masters often become out of synchronization and
> this causes many more problems.
>
> Has anyone worked on some similar project or has pointers to this problems
> ?
>
> Thanks,
> Bhavesh
Received on Fri Jun 11 1999 - 10:43:33 CEST

Original text of this message