I do all of the database metadata updates in my application's code, not with
scripts. I have a settings table. One of the settings is the "Database
Version". I define those numbers myself. When the application starts, the
first thing it does is query the settings table to find out what the current
database version is. The application knows which data version it should be
on, so if there are updates to be made, it simply executes the appropriate
SQL commands, updates the settings table for the new data version, and
continues starting the application.

-Joe

Todd Brasseur wrote:

> We are trying to decide how to handle keeping our clients databases
> metadata the same as ours.
>
> We have a production database in our office which we are continually
> changing as our product evolves. Our clients have their own copies of
> the database with their data.
>
> Every once in a while, we give them a new 'release of the software'
> which includes the new program along with updates to the database. We
> are finding it quite alot of work to maintain 'change scripts' to run
> against our clients databases. The most work is in keeping track of
> which scripts have been run against which clients databases.
>
> Does anyone have a similiar situation? Any ideas regarding how to
> manage the database changes would be greatly appreciated.
>
> Todd Brasseur
> COMPASS Municipal Services Inc.
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/