We have a select on LTAP which has millions of rows ... One of the columns (present in the secondary index) used in our select query is highly skewed (Y/space) . Entries with space is couple of hundreds... We could use substitute literals hint to force the query to use the correct index... This table's statistics is generated with histograms.
I saw the blog about using adaptive cursor by Stefan Koehler and that we can use database parameter to turn on the Adaptive cursor. The question is does this make sense to resolve any of the issues like above.. Or would it make better sense to perform coding changes (sometimes in Standard SAP code) on a case by case basis.