OPTCOMPIND

Posted in 2006

tomcaml@yahoo.com — 27 Jun 2006 11:11:15 -0700 — source: Usenet: comp.databases.informix

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!!! Superboer. =================================== We currently have it set to 2 and very much an OLTP system - can anyone shed light, experiences, etc on this setting? Tom

↪ replying to tomcaml@yahoo.com

Art S. Kagel — Tue, 27 Jun 2006 16:42:21 -0400 — 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!!! > > > Superboer. > =================================== > > We currently have it set to 2 and very much an OLTP system - can anyone > shed light, experiences, etc on this setting? > > > Tom > Most users with OLTP servers keep OPTCOMPIND set to zero (0) as the resulting nested loop joins result in lower system resource use, fewer sorts and temp table builds and better response times. Art S. Kagel