Re: [Firebird-devel] Firebird Transaction ID limit solution

[Dimitry S. <sd...@ib...>]

03.01.2012 19:44, Ann Harrison wrote:
> I'm not sure that either replication or the
> mechanism Sean is proposing (similar to either the start of a shadow
> database or nbackup) can solve the overflowing transaction id problem.

   Simply: let's say we have two synchronous database. One is primary and the second is... 
well... secondary.
   When transaction count reach, say, 1000000000 transaction, we shut down replication and 
perform backup-restore of the secondary database. Then we continue replication and after 
some time we again have two synchronous databases. In primary database transaction counter 
is big, in secondary - low.
   Now we switch the roles. Primary database become a secondary and vice versa. After then 
we can repeat previous step to reset transaction counter in ex-primary database without 
stopping whole system.
   Voila.

-- 
   SY, SD.