Re: INSERT performance problems

Probably. I have other options, though. It seems that with indexes enabled, performance degrades as the transactions get larger. So if I leave the indexes enabled, but just split the load into, say, 30 or 40 smaller transactions, I might buy back some time. RG <rag4@mead.com> wrote in message news:3709708C.1A68@mead.com... > Thomas J. Girsch wrote: > > > > All of these have been done, except for LRU_MIN and LRU_MAX, and CKPTINTVL. > > I'm reluctant to set those as such, because this is normally a heavy OLTP > > system (not a warehouse). I just have this one exception where a nightly > > job needs to do a large "posting." > > > > Is there any way to change these parameters dynamically, without taking the > > engine off-line? > > > Not as far as I know. I have heard of some people maintaning two or > more onconfig files for situations like yours. If you have the onconfig > files already prepared, the bounce is a pretty quick thing. Give your > oltp users plenty of warning and give it a go (easy for me to say, > right?!). I imagine they are seeing some pretty poor performance when > the index builds are occuring anyway??? As soon as the index build is > over replace the onconfig file with the original and bounce again. > > Looks like this is your only other option? > > Robert > >