Subject | Re: [firebird-support] Getting ready for moving to production? |
---|---|
Author | Ann W. Harrison |
Post date | 2005-02-23T16:26:12Z |
rjschappe wrote:
succeeds, you use the new version of the database and discard the old
one. In that case, there's no need to clean up the old one before
throwing it out. The bits all end up in the same bit bucket.
part of the restore. Essentially a gbak backup unloads first the
metadata, then the data from your database into the backup file. A
restore creates a new empty database, defines domains and tables, then
stores all the data, then activates constraints, triggers, indexes, etc.
Ann
>If I understand, you're doing a backup and a restore. If the restore
> During testing we have been (every night) deleting all the records off
> of most of the new FB tables/database and then pumping over around 1.3
> million records...
>
> I do a backup with -g and then a restore... however is there anything
> else that I should do prior to releasing this for real???
succeeds, you use the new version of the database and discard the old
one. In that case, there's no need to clean up the old one before
throwing it out. The bits all end up in the same bit bucket.
>Again, if you're using the new database, all those things are reset as
> I am not sure... but like reseting the last active trans, oldest
> trans, updating the statistics, etc....???? (there is some worry that
> our home-built data-pump may not be cleaning up after it's own
> transactions very well...)
part of the restore. Essentially a gbak backup unloads first the
metadata, then the data from your database into the backup file. A
restore creates a new empty database, defines domains and tables, then
stores all the data, then activates constraints, triggers, indexes, etc.
>Regards,
Ann