Re: OPTCOMPIND

Posted in 2006

Madison Pruet — Tue, 27 Jun 2006 16:25:42 -0500 — source: Usenet: comp.databases.informix

tomcaml@yahoo.com wrote: > Hi all, > >>From a post by Superboer. : > > OPTCOMPIND 2 # To hint the optimizer> > for oltp do not set it to 2 set it to 0 instead!!! Basically - when we implemented hash joins, we had issues with the optimizer costing of hash joins vrs nested-loop joins. So OPTCOMPID was implemented as an optimizer hint to specify that we wanted to give preference to nested-loop joins. Generally shops which tend to be OLTP will set OPTCOMPIND to 0. Of course, if your application is not performing joins, then it probably doesn't matter what it is set to. > > > Superboer. > =================================== > > We currently have it set to 2 and very much an OLTP system - can anyone > shed light, experiences, etc on this setting? > > > Tom >