28.11.2013 14:26, Jiri Cincura wrote: > The replication might work, but as I know how the updates are flowing, > we would very likely had a lot of collisions.
Only if database was designed this way. Properly designed databases should not produce conflicts. > But the real problem is switching from old to new and vice versa. > There's maybe 50 different applications running using this database > (some even from PSQL). As I can do step by step from old to new, when > disaster happens (and it will) I would need to switch back quickly > (and I mean really quickly). Not a viable path with 50 apps. As quick as changing DNS record for new DB server to old IP address?.. -- WBR, SD. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
