hi all,
COSP table has 13 fields as primary key.
we have a report which has a select query which accesses this table with first 6 fields as a criteria in where clause. all 6 fields are used (non of them are blank) and hence considered in the select query.
but the table has huge number of entries: more than 35 million
hence the report takes around 7 hours to execute, hence its run in background. but business is not happy with the performance of the report.
The table is being archived on monthly basis (using the appropriate criteria)...
I can not create index, since the 6 fields in where clause are already part of primary key (hence it gives error on syntax check and tells the index will be never used..)
Since the report is used on monthly basis, i doubt if i can use the buffering option (i guess the buffer will be too large, hence impacting overall performance of the system...) {if i can use the buffering option, please let me know}
Since the table has so many entries, i am not able to use "select-into-itab" option, i have to use "select-endselect" to avoid memory dump..so, no further tuning through code changes is possible!
here i am running out of options to performance tune this report, please suggest some way to solve this issue..
Edited by: chinmay kulkarni on Nov 28, 2008 10:27 AM