Milan Babuskov has written an interesting paper about your problem:

http://fbexport.sourceforge.net/
follow "Managing Metadata Changes".

I have followed his advice and I have developed a satisfying solution.
The only difference is that I keep all the scripts in a separate
database for easier handling. Using 800 Kb for a few scripts might seem
overkill, but using a page size of 1 KB for this database reduces the
size to less than 300 KB.

Fulvio Senore


mlq97 ha scritto:

> I am trying to figure out a strategy for upgrading deployed databases
> that will be part of a packaged commercial product.
>
> I am assuming that I will have a SQL update script which reads the
> target version and contains sections to incrementally upgrade from the
> target version through all the intermediate versions to the current
> version.
>
> Is there a tool to run these scripts and also have error messages to
> alert users (or the upgrade installer) if any step of the upgrade
> process failed? Is it usual in these circumstances to roll back all
> the changes?
>
> How do people normally handle the DB upgrade issue?
>
> Thanks
>
> Mitch
>
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>