From my little knowlegde i would guess Robert is talking about the
delta between the oldest active transaction and next transaction.
But as long as i do not know anything about the application (event
listeners, long time transactions and that) and the environment (Number
of active connections and that) Robert writes about (may be he has in an
earlier post) , it is just peeking around.

just my EUR 0,02, Marcus
Alexandre Benson Smith wrote:

> Em 5/6/2013 13:33, Leyne, Sean escreveu:
>> Alexandre,
>>
>> While I completely agree with your points. I read the OP as meaning
>> that they are running out of transactions ID (given the current 2GB
>> limit) -- they have an 800GB database, so a large number of
>> transactions would/could be expected, so transactions ID could get
>> exhausted. In that case, a backup/restore would be required, but a
>> weekly cycle is excessive (it means that the db is handling more than
>> 3550 transactions per second!!! Very unlikely). Sean
>
> Hi Sean !
>
> I read that, but the point I was talking about is related to this phrase:
> "It became clear to us that to keep the system going we have to run a
> backup/restore every weekend because of slow downs when transaction
> counts got too high"
>
> But I don't think that the transaction count getting too high would lead
> to a server slowdown.
>
>
> see you !
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>

[Non-text portions of this message have been removed]