Re: dbexport/dbimport problems

You're right. I just checked on Online 6.00UE1. dbimport creates the index after loading the table. In which case I suggest that if you are loading a large table that will span multiple disks, you do them manually using LOAD. I've received a few e-mails asking why so here is the reply: Let's say that you have a table that spans 5 disks and the index accounts for 20% of that. If you load the data with no index, the table will fill the first four disks. When you index the table, this will fill up the last disk. When users start using this table, each indexed access will read 5 (say) index pages from the last disk and one page from one of the other four. Therefore the last disk will be accessed 20 times more than the other four causing a bottleneck David W Chan Objective Research Ltd dwc@cix.compulink.co.uk