RE: Large delete
Jack Parker wrote
>
> Guess I wasn't clear enough.
mostly snipped ....
> don't forget to
> update statistics on the new table and re-create any indices.
And for good measure update statistics for procedure in case the table
is called by any stored procedures.
>
>
Colin (better late than never) Bull
c.bull@videonetworks.com
sending to informix-list
Thank your for your effort, but we don't use any stored procedures, since
application is written in some strange tool called Systemator, which doesn't
know anything about stored procedures (and many other things as well for
that matter).
Anyway, we have finished the job this weekend - successfully! Thank you all
for your help!
By the way: we used HPL. First it looked, we'll not get through, but after
we reduced BUFFERS setting in onconfig file from 2M to 20K, expanded
RA_PAGES to 128 and RA_THRESHOLD to 120 (64/60 normally in our environment),
we experienced 5-times speed improvement(!!). I would recommend that you
drop and recreate indexes manually setting PDQPRIORITY to 100, since I'm not
sure, how HPL does it (disables indexes before load and reenables them after
load, but is PDQPRIORITY set?).
Gorazd
"Colin Bull" <c.bull@videonetworks.com> wrote in message
news:bnjg84$1jl$1@terabinaries.xmission.com...
>
> Jack Parker wrote
> >
> > Guess I wasn't clear enough.
> mostly snipped ....
> > don't forget to
> > update statistics on the new table and re-create any indices.>
> And for good measure update statistics for procedure in case the table
> is called by any stored procedures.
>
> >
> >
>
> Colin (better late than never) Bull
> c.bull@videonetworks.com
>
>
> sending to informix-list