Subject [firebird-support] Re: Best way to copy records from a FireBird DB table to another FireBird DB table
Author Svein Erling Tysvær
I don't think there is anything inherent in Firebird that can help you, what some people do, is to have a table simply containing one record saying which version of your database is installed and then create upgrade scripts for changing from version A to B. If a user wants to upgrade from version A to C, then they first run the upgrade script from A to B and then B to C. Of course, before doing such an upgrade, they minimum encourage the user to take a backup in case things doesn't work out correctly. And the program running the upgrade script ought to have the only connection to the database at the time of upgrade (though the risk may be small for data loss if several are connected, I think there is a higher chance of errors when mixing DDL and DML than if you do DDL only when no others are connected).

How to write the upgrade script? Well, either keep track of all DDL changes you do or write the script manually before releasing a new version (comparing the DDL of the old and new version).


-----Original Message-----
From: [] On Behalf Of LtColRDSChauhan
Sent: 2. mai 2010 03:05
Subject: Re: [firebird-support] Re: Best way to copy records from a FireBird DB table to another FireBird DB table

Thanks for your reply.
I was looking for a solution through Firebird itself / FlameRobin / .NET
Provider please.

On Fri, Apr 30, 2010 at 7:35 PM, cornievs <cornievs@...> wrote:

> Hi
> I use the following solution. I use a tools like IB Expert to change the
> metadata and log the changes to a file. These changes I then save in
> different DB with a table with field that has the metachanges and a field
> with a version number. On application start up I check the version to that
> the programs requires and if required run the metadata changes on the
> customer Db.
> Hope it helps
> --- In<>,
> "RDS" <rdsc1964@...> wrote:
> >
> > Hello,
> > I please need support on the above issue.
> >
> > I have deployed an application for which features have yet not been
> freezed. Hence my database keeps changing - mainly as addition of fields to
> tables, addition of tables, addition of stored procedures. Hence when i
> deploy new versions of my application, back up and restore will not work.
> >
> > Thanks and regards,
> > Lt Col (Retd) RDS Chauhan