Optimize Method Q?

Hello Folks,

Ok, I know that I have alot to learn, but when you do something believing that it will speed up things and it does but only for "some queries" and turns others into instant snales, a newbie like me really wonders.

The situation is like this, I analyzed all the relevant schema's tables and indexes. Now one of the more important queries( a long one) just turned from a tortois into a snale. I have been forced to set the database optimizer method to rule. Which has had the effect of turning the snale back to a tortois.

The system is a 8.1.7
on a Windows 2000 machine.
Optimization was CHOOSE, but because the tables were not analyzed it invariably chose rule.

The only "strange" observation I can make is that the developers have three indexes on this table, with three columns in all three indexes, but in different positions.

Any comments on why this would happen/how this happens.

This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal -
For more information please visit

      <A
href="http://www.marshalsoftware.com">www.marshalsoftware.com Received on Mon Jan 21 2002 - 08:25:08 CST