>>How about redirecting the auditing of the import into a readwrite cursor based on the audit table, then when import is done, append from it into the audit table? You could wrap it into two levels of transaction (well, maybe), the inner handling the import only, and if it goes right, then do the append audit too. Since the audit isn't really triggering anything else, the append should be smooth and fast.
>
>I'll have to try it, but the procedure sounds ... well, it sounds sound.
>
>Did you ever encounter any similar problems in your own applications?

Not really - the large imports and busy networked apps usually managed to live in separate universes. I was lucky.