Skip to Content
0
Former Member
Feb 28, 2006 at 10:58 AM

Problem on secondary Index

201 Views

i am fetching data from NAST table.

SELECT MAX( DISTINCT ERDAT ) FROM NAST
                             INTO VAR_ERDAT
                             WHERE OBJKY EQ '4500016332'.

When i chkd in SM50 Process analysis,It is reading NAST table Sequentially,Which is taking long time.

When i checked in SQL tracer,It is not using the secondary index that it shud use for NAST table,What i know is...ABAP optimizer itself decides on Secondary Index which is to be used,What we can do is use the Secondary Index fields in Sequence as defined in Secondary INdex.

ACCORDING TO MY UNDERSTANDING :

SECONDARY INDEX THAT SHOULD BE USED according to select Statement that i wrote above FOR NAST TABLE:

<b>INDEX ID : ADQ

SHORT DESC : ADABAS-Specific Index</b>

Please correct me,if i am wrong somewhere.Also tell me if there is any way of explicitly forcing it to use the proper SECONDARY INDEX.

THANKS IN ADVANCE,

VIJAY RAHEJA