Adam wrote:

>
>>How about copying an *.fdb while transactions are running and later
>>just copying it back?
>
>
> It is probably more robust than you give it credit for. My guess is
> that there will be a lot of stuff that will need to be garbage
> collected, but it is unlikely to be a problem in my experience. Still,
> don't do it.

The robustness of Firebird isn't the problem when copying a running
database - no file that has random access to interrelated parts can be
copied while it's active. If you start and commit a transaction during
the copy and the tip is at the end of the database (which is probably
will be), your copy will have a header that says that the transaction id
is available and a tip saying that it's committed. Not at all good.

>
>

Regards,


Ann