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

[Ann H. <aha...@nu...>]

Dimitry,

>> - a "data port" utility which would allow for data to be ported from a live database to a new database while live is active but would need a finalization step where the live database is shutdown to apply the final data changes and add FK constraints.
>
>   And exactly this utility is called "replicator". If made right, it doesn't need FK
> deactivation and can do "finalization step" when new database is already in use.
>   Aren't you tired inventing a wheel?..

Different vehicles need different wheels. The wheels on my bicycle
wouldn't do at all for a cog-railway and cog-railway wheels work very
badly on airplanes.  Airplane wheels are no use at all in a
grandfather clock.  Engineering is all about creating new wheels.
Right now, what we're looking for is a wheel that can reset
transaction ids.  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.

Cheers,

Ann