RE: ESQL/C -Insert- Performance

From: a_blonde@mindless.com > > ---- you wrote: > > Try dropping some or all of your indexes and then recreate them after >the > > inserts have finished. > > You may find that this is quicker. You may also have to run an update > > statistics on your table > > after you've re-created your indexes. > >I am not too clear on this Dude. Are you saying that every 2 hours, they >should drop all indexes, load 75000 records, then create 5 indexes on over >8 million records, and all in under 2 hours? Yep, that's what he said. And of course, render the database inaccessible during the process. I'm guessing by the domain (orange.be) that this is a company Rekaish should have a useful answer for. I'd honestly hope so! :-) To return to the original question: why worry about batch loading? Why not trickle feed the table continuously? Give the loading program a low priority and set lock mode to wait... ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com