Re: Optimizing a BaaN installation

Claus Samuelsen said: > > david@smooth1.co.uk wrote: >> What does unloading and loading tables cause problems? >> >> Surely you put back the same data that you have before? >> >> If not what unsupported crap are Baan doing? >> >> I should add this to the FAQ! >> > > When using level 1 driver BAAN calculates hash keys. These key values > are stored as binary data in char columns, so unloading/loading these > values are not safe. > dbexport/dbimport has a -X option which treats binary data in char > columns as hex representation. > Using 'unload to'/'load from' will most likely change the hash key values. > BAAN has tools for unloading/loading tables. It's slower than the > informix unload/load, but BAAN recalculates the hash key values! I'm surprised that no-one has suggested "uninstalling Baan" as an optimization mechanism. -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien ` dire qu'il faut fermer sa gueule" - Coluche did i mention i like nulls? heck, i even go so far as to say that all columns in a table except the primary key could/should be nullable. this has certain advantages, for example, if you need to insert a child record and you don't have a parent row for it, just do an insert into the parent table with the primary key value (everything else null), and voila, relational integrity is preserved. but this is, admittedly, a bit controversial among modellers. --r937, dbforums.com sending to informix-list

That was my first option my boss rejected (something about the money they spent. i'm not really sure because i wasn't listening to her :)