Skip to Content
Feb 22, 2011 at 04:23 AM

Usage of Sorted Keys in standard tables



If I have a sorted secondary key (unique or non-unique) in my internal table, and use the secondary key with my DELETE statement (DELETE ... WITH TABLE KEY <secondary_key_name> COMPONENTS ... = ...), I still get a prio 2 checkman error saying possible sequential read. My question:

1. What's the difference between usages of sorted key and a sorted table with regards to a READ statement?

2. Would I still have to do a SORT on the standard table by the secondary key components and then do a BINARY search to avoid the possible sequential read? (in that case why should i mention the key to be "sorted"?

Thanks in advance,

Best Regards

Anantharaman L