25.03.2015 12:20, Tim Ward wrote: > The fix in 3.0 sounds good! - but it'll be a while for us, we're > currently looking at upgrading to 2.5.
Instead of going for the -o switch and losing one table completely, I'd rather use the -n switch. As a result, you have all data but some constraints are missing. Then generate the metadata script for the resulting database, compare it with the original one (yes, you should have it somewhere in VCS), generate an upgrade script (I suppose IBExpert is able to create one) and fixup your restored database. Maybe not a piece of cake and can hardly be automated, but it provides you with a valid database. Dmitry
