Subject | Re: [firebird-support] GBak -O option |
---|---|
Author | Ann W. Harrison |
Post date | 2008-10-14T22:13:42Z |
Andrew Stuart wrote:
transaction. That's fine, unless one of the tables has an error -
shouldn't happen but it can, if, for example, someone figures out
the trick to making a field smaller, but hasn't the native wit to
insure that the stored data fits the new definition. In that case,
the failure to restore one table will rollback the whole database.
The -o switch puts a commit after each table, so you get something
back even if you've been too clever for your own good. (Or the
data has been corrupted by something other than your inventiveness.)
It's a recovery mechanism, not a normal operating mode.
Good luck,
Ann
>Yes.
> Can someone explain the usefulness of the -O One table at a time
> option?
>
>Normally, Firebird restores all the data in a database in a single
> I've noticed we have been using it in our restore scripts so I tried it
> without the -o option. This halved the restore time, and everything
> else seems normal, tho I've only tried it once
>
transaction. That's fine, unless one of the tables has an error -
shouldn't happen but it can, if, for example, someone figures out
the trick to making a field smaller, but hasn't the native wit to
insure that the stored data fits the new definition. In that case,
the failure to restore one table will rollback the whole database.
The -o switch puts a commit after each table, so you get something
back even if you've been too clever for your own good. (Or the
data has been corrupted by something other than your inventiveness.)
It's a recovery mechanism, not a normal operating mode.
Good luck,
Ann