> -----Original Message-----
> From: owner-informix-list@iiug.org
> [mailtowner-informix-list@iiug.org] On Behalf Of jleffler@us.ibm.com
> Sent: Wednesday, February 11, 2004 11:53 AM
> To: informix-list@iiug.org
> Subject: Re: Whatcha' wanta have?????
>
>
> mosserp@wellsfargo.com wrote:
> > Related: Implement outstanding feature request to run "set
> optimization low"
> > from the *server* side.
>
> Can you elucidate this, possibly with the feature request (bug)
> number? Are you saying that you cannot run SET OPTIMIZATION LOW in a
> stored procedure? The request has to be processed by the server, so
> I'm confused...
>
> -=JL=-
>
165421 FEA: ALLOW SET OPTIMZATION LOW FOR STORED PROCEDURES TO BE TURNED ON
DYNAMICALLY FROM ENGINE SIDE

We have an extremely critical high-txn-volume HA app that relies very
heavily on SP's. When we run update stats (we use dostats), the SP's have
to be re-optimized A LOT while the stats for the tables are being updated.
This causes slowdowns and lock contention (catalog tables locked while SP is
re-optimized). An "update statistics for procedure" *is* run after the
tables are all done.

Rather than putting "SET OPTIMIZATION LOW" in all of the application code,
it would be much better to be able to flip a switch in the engine (onmode
command??) that effectively turns on SET OPTIMIZATION LOW for *all* SP's,
until the switch is turned off again.

Is that more clear?

Thanks,
Paul Mosser
sending to informix-list