Alan McDonald wrote:

>> To quote Helen "bad things will happen" when the Transaction ID overflows.
>>
>> (The Firebird Book p512 for details)
>>
>> Adam
>>
>
> of course this could be an issue..

...snip...

> Someone else is arguing that 700,000 per day is large... that's 8
> Transaction per second
> that's 8 years life before a backup/restore.
> Bottom line - know your transaction rate and act accordingly.... agree?
>
> Alan
>

I have read in devel list that is a planning to roll the transaction
numbers back and provide additional inteligence to MGA to handle it, Jim
said is not to hard to implement, but AFAIK it is just superficially
discussed, so I don't expect it for 2.0. That question was raised by Ann
for a problem just like this, a heavy used database, that could reach
the 32 bit limit in a not too long period of time...

Another option is increase the transaction to 64bits, but this you
increase record size, lower the density on transaction information pages
and so on. IIRC not a good option, I think the sollution will be add the
required mechanisms to handle the transaction overflow/rollover
transparently.

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br