My problem is, that i want to test the index generator.
For that I’m using an sql with an bad full table scan on a table with 400000 rows.
I increased the level of the index generator to 5 and it still doesn’t give any new index sets…
but it says that i should use the sql rewrite function when tuning only one statement plus the optimize indexes module always freezes when i try to optimize the single statement.
Optimize Index use different approach to find indexes, sometimes it can find indexes that our single index generator cannot find.
SQL cannot use indexes may due to at least two reasons, the syntax itself forbid an index usage or Oracle SQL optimizer think that not to use the index is the lowest cost choice. If you really want to try that table with 400000 rows only, you can create a physical index on that table base on your SQL access columns, and then paste your SQL to our SQL Rewrite to look for a SQL with that index used and check whether this alternative is faster. Have you try our rewrite on your SQL ?
I would like to know whether the “User Index” is still work for your SQL ? You can define a virtual index on repertoire_code to check whether the virtual index function is still working.
Are there any SQL you in your database can generate index recommendation from our product ? or it is no index recommendation for any SQL at all ?