> 03.01.2012 18:51, Leyne, Sean wrote: > > - 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?..
As Ann poetically replied, there are different wheels for different vehicles. I was/am thinking that replicator requires more setup than a multi-threaded data pump utility would. The problem is not a perpetual problem, it is relatively one- time only. As for the FKs, I see the tool as being a some which needs to have the maximum performance. FKs are required for referential integrity but they slow down bulk move operations, since the FK values needs to be checked. Further, since the data integrity would already be enforced in the Live database, the target database would not need FKs until the "go live" pre-launch. Also, FK would require that the database schema be analyzed to process tables/rows in the correct order, which is an obstacle to maximum performance. Sean ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
