I think Svein's suggestion is a great practice if you have external users. There was a great article on in a couple of years ago but I cannot find it now. That article suggested that you only make official structural changes to a special master copy of the database that reflects your most recent version of the database. Rather than making the changes directly to the database, you make the changes to your working copy. When your working copy performs as required, you use a tool like IBExpert's Database Comparer to produce a script that will update the master copy of the database. Those scripts should get a version number and that version number should update the version number in the master database. You can then use that version number to run updates like Svein suggested.

If you don't have a lot of external users, the IBExpert Database Comparer tool can actually make the updates after creating the script. This may be available only in the paid version of the tool. It's the best tool I have found for Firebird databases, it's not too expensive. The only downside is that the payment process is pretty archaic, but I have done it a couple of times now and it worked ok.

Jack

--- In firebird-support@yahoogroups.com, "Steve Cookson" <it@...> wrote:
>
> Hi Guys,
>
> Is there some way I can compare the metadata between two databases?
>
> Really I'd like to implement configuration management for my Firebird user
> base, but I don't really know how to begin.
>
> Any ideas would be welcome.
>
> Regards
>
> Steve
>
>
>
>
> [Non-text portions of this message have been removed]
>