Re: PDQPRIORITY

I want to agree strongly with Krishna - PDQPRIORITY 100 can and does help, but it can NEVER solve serious performance problems, since it may give you another 30% or so, but only at the expense of other concurrent processes. I can almost guarantee you that either some needed indexes are missing, or that the query optimizer is failing to use a needed index and is instead performing a serial table scan. Since the query optimizer bases its plan on the distribution statistics, performing an update statistics as described in the Informix tuning manual can often make a dramatic performance improvement. If you can, compare the optimizer's query plan on the 7.2 database to that of the 7.3 database - most likely, you will see significant differences. News wrote: > Try running update statistics for all your tables. Also, look in the manual > and follow their advice for any columns that head or are a part of an index. > This will work wonders. > > krishnakn@my-deja.com wrote in message <7nansr$vt9$1@nnrp1.deja.com>... > > > > > >Hi, > > > >We are facing a lot of performance problem in informix 7.3 > >Application was running fine till we moved from 7.2 to 7.3. > > > >Someone suggested set pdqpriority to 100. > > > >The application is written in esqlc. > >The maxpdqpriority is set to 100 in the server. > > > >I've set the pdqpriority to 100 in the application by > > EXEC SQL prepare d_id from "set PDQPRIORITY 100" ; > > EXEC SQL execute d_id; > > > >But when I execute the application, I get the error saying > > > >ERROR MESSAGE: Cannot support multiple connections over shared memory. > > > >How should I set the pdqpriority in the esqlc program ???? > > > >Pl. help me out ... > > > >Thanks > >krishnakumar > > > > > >Sent via Deja.com http://www.deja.com/ > >Share what you know. Learn what you don't. -- Richard C. Auslander Database Manager AirFlash, Inc. 1733 Woodside Rd., Suite #110 Redwood City, CA 94061 (650) 556-7928 www.airflash.com