> I have an application which is writing every second the same record in
> a table with many colums. Each update is commited. I can observe that
> the memoryusage of fbserver increases and after a few hours windows
> starts to swap. fbserver uses 100% of CPU and the whole system stops.
> I'm using firebird 1.5 under Win XP.

Perhaps the problem is not the update itself ?
Is it possible that you allocate statement handle for each execution
but do not release it ?
Perhaps some trigger is involved ?
Transaction ids indicate that you do not use Commit Retaining, do you ?

Ivan
http://www.volny.cz/iprenosil/interbase/

> Difference of oldest transaction, oldest active transaction and next
> transaction is 1, so there's no problem with long running transactions.
> I've tried to increase the intervall of writing, but that doesn#t
> solve my problem it only pushes back the time of crashing.
>
> Any ideas how to solve this problem?