Hi,
It mentions in the documentation that an index can be explicitly hinted
within a query -

*http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#perfdiagqueryplans*

***If the index choice is not the right one, consider the following
possibilities:*

   - *Run statistics. This is not always necessary because the database
   takes dynamic samples but it can help in cases.*
   - *specify the desired index explicitly with table option.*
   - *Use literal constants instead of parameters, specially if the query is
   long running and values of the columns being compared are not evenly
   distributed.*
   - *To exclude index usage for a column, write col + 0 =xx.*

How do I do this?

It also mentions ensuring the statistics are up to date. Can this be done
within conductor? Or is the best way to drop and recompile the index?

Cheers
Mark

Reply via email to