Frosty the Coder
Legendary Poster
I have a custom table w/9,076+K rows in it.
I have it joined to F4211 which has 578+K rows.
I have the custom table as the "left" side F4211 is the "right" side.
They are joined by KCOO, DOCO, DCTO.
The custom table has addl keys beyond this.
Data selection in the UBE is a series of
"where ((F55COL = value) and (F4211 MCU = value1))
OR (F55COL = value) and (F4211 MCU = value2))...
These are set in the INIT er for the section using the bsvw.
When the ube reaches the point of processing this sql
it, understandably, grinds to a near stop.
My FIRST fix will be to clean up the custom table,
reducing the number of rows to as few as possible.
Even after I do this, this table will be large.
Is there anything I can do either in the join,
or when I'm setting the data selection to improve this sql?
TYVM
Gene
I have it joined to F4211 which has 578+K rows.
I have the custom table as the "left" side F4211 is the "right" side.
They are joined by KCOO, DOCO, DCTO.
The custom table has addl keys beyond this.
Data selection in the UBE is a series of
"where ((F55COL = value) and (F4211 MCU = value1))
OR (F55COL = value) and (F4211 MCU = value2))...
These are set in the INIT er for the section using the bsvw.
When the ube reaches the point of processing this sql
it, understandably, grinds to a near stop.
My FIRST fix will be to clean up the custom table,
reducing the number of rows to as few as possible.
Even after I do this, this table will be large.
Is there anything I can do either in the join,
or when I'm setting the data selection to improve this sql?
TYVM
Gene