The explain output of the statement: SELECT COMPANY_ID,COM_NAME FROM COMPANY ORDER BY COM_NAME ASC
shows that a table scan is being performed. Now I know there was mention of this in previous emails and one suggestion was to look at the optimizerstatistics tables to see if the system sees a table scan as more efficient. Well I did and the use of the index defined on COM_NAME is clearly more efficient but sapdb still decides to use a table scan. The index was rebuilt, the statistics for all tables updated using the dbmgui and still no change. Can anyone tell me what version of sapdb/maxdb this problem was resolved in? Thanks, Kevin
