Rajat Sharma
Member
Thanks Tom, MadDBA,
I have found WHOLE-INDEX issue with FIND LAST statement (that we discussed yesterday) but I didn't understand that why we are creating one index for n number of fields?
For ex:
I have one table c-data having 25 fields and one index c-index. Index c-index contains 5 fields of table c-data. But why, we are creating a single index for many fields because only the first field in the index list (leading component) will do effective table scan (when used in where clause) and rest all will perform complete table scan (WHOLE-INDEX). Isn't it be more effective if we define four indexes for four fields (I know it wouldn't, but why)?
Is it a kind of composite primary index which is a combination of multiple fields ?
Please suggest.
Thanks & Regards!
Rajat.
I have found WHOLE-INDEX issue with FIND LAST statement (that we discussed yesterday) but I didn't understand that why we are creating one index for n number of fields?
For ex:
I have one table c-data having 25 fields and one index c-index. Index c-index contains 5 fields of table c-data. But why, we are creating a single index for many fields because only the first field in the index list (leading component) will do effective table scan (when used in where clause) and rest all will perform complete table scan (WHOLE-INDEX). Isn't it be more effective if we define four indexes for four fields (I know it wouldn't, but why)?
Is it a kind of composite primary index which is a combination of multiple fields ?
Please suggest.
Thanks & Regards!
Rajat.