Re: Question on 7.12 Optimizer

We had a similar problem. 7.12 on Data General. This was solved by reorganising the index strategy and query. (Simply moving field selection and join sequence and moving an un-necessary composite index field). *NB: Workaround (IMHO): We also found that update statistics high DROP distributions (As opposed to update statistics high which is supposed to auto. drop distribs) solved the problem. If one of the queried tables used had too many rows inserted, the optimisation strategy changed back to the bad one. Mark D. Stock <marks@west.co.za> wrote in article <339B2197.6DAD@west.co.za>... > Paul Kapp wrote: > > Lam Yin Yui wrote: > > > V Crouch (tiger@sky.net) wrote: > > > : The mystery is this: On test, my query uses the index, while the prod > > > : query does a sequential scan. > > > I also face this problem on update statistics medium or high. In my opinion, if you would like to use index searching, you better update statistics medium; though the performance may not be optimize.