Re: IDS2000

Scott O'Rourke wrote: > > OPTCOMPIND is set to 0 OPTCOMPIND = zero will cause the optimizer to tend to favor nested loop joins. Try 1 or 2. Art S. Kagel > I can't remember what sort of joins were being made before (sorry!), but I'm > fairly sure they weren't nested loop joins, and it is definetly slower than > before. > > Queries that used to take 40 - 50 seconds now take 2 or 3 minutes. > > Thanks for any help! > Scott. > > "William Rice" <william.rice@sabre.com> wrote in message > news:39B79812.AA9622B0@sabre.com... > > Scott wrote: > > > > > Hi, > > > I'm having a problem with the query optimiser in IDS.2000. > > > After upgrading from 7.3 to IDS.2000, a lot of our 4gl applications > seemed > > > to be running slower. > > > After running with set explain on, a lot of the queries were using > nested > > > loop joins. > > > I've tried all sorts of update statistics and optimiser directives, but > > > cannot seem to avoid them. > > > Even the simplest joins on unique indexes run in dbaccess seem to use > them. > > > Has anyone else had this problem, or does anyone know how to get round > it? > > > > > > Thanks for any help, > > > Scott. > > > > What type of join were they using previously? > > What is OPTCOMPIND set to? > > > > Do you have an approximation on the speed difference, instantaneous to 2 > > seconds ... > > > > Hope I can help, > > Will > >