At 12:35 AM 29/06/2006, you wrote:

>Adam wrote:
>
> >> A big part of the performance hit here is occurring because the input
> >> file is huge. Processing the entire file (up to half a million
> >> records involved) in one call to the SP will cause the undo log to
> >> build up and build up until the engine simply abandons it, i.e. all
> >> that resource deprivation comes to naught. The undo log is a Good
> >> Thing (TM) for a reasonable-sized batch, because it allows the engine
> >> to clear out new records in case a rollback happens, thus avoiding
> >> the survival of garbage when inserts are abandoned.

Actually, Adam didn't, I did.

>Err, well actually, the undo log for a procedure can't be abandoned
>because the procedure is considered a single atomic statement - if
>it fails, Firebird must be able to remove it and all its side effects.

Ach, of course.

./heLen