Re: Converting large amount of data

I don't know now - would have to check the archives. I think I was responding to your statement - hope I have that right - about if you open an S/O LF an index is always created. If it is in the context of DBU, then I don't know - we use DBU, the 3rd-party tool. There are ways in which it seems to use SQL as the mechanism for retrieving data - F15 lets you specify the WHERE clause.

Nonetheless, there've been many interesting ideas presented in this thread, I think.

Best regards
Vern

On 3/11/2021 4:56 AM, Gad Miron wrote:

Yeah

I thought the OP dealt with opnenin a file using DBU
which is (I think) non-SQL tool.

HAND
Gad

date: Wed, 10 Mar 2021 13:08:21 -0600
from: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: Converting large amount of data

Brace yourself for just a bit more TMI - not sure you are suggesting
this, but we are told not to use any LF in the SELECT statement. If we
do, the optimizer goes out to find the PF, then does what it would have
done to find the best plan.

Basically, the optimizer won't use an LF just because we put it in the
SELECT table list.

I believe DYNSLT is more relevant for non-SQL IO. Maybe we are talking
at cross-purposes, however.

Cheers
Vern

On 3/10/2021 11:36 AM, Gad Miron wrote:

Vern

TMI indeed

I figure that a large DYNSLT LF with a large number of records that do

not

meet the Select/Omit criteria will cause this phenomenon. .