Re: Slow Query Performance from the Web

Corissa,

What does the SQL statement look like that creates the view?  I suspect
if the bottleneck is in the SQL it's there, not in the one you posted.

Also, could you list the indexes with their keys over all files involved
in the view.  That would help a lot.

As Matt suggested, if you can run it under debug the optimizer will tell
you if it has a problem.

Rick

> -----Original Message-----
> From: web400-bounces@xxxxxxxxxxxx
> [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of
> Matt.Haas@xxxxxxxxxxx
> Sent: Wednesday, April 19, 2006 2:55 PM
> To: web400@xxxxxxxxxxxx
> Subject: Re: [WEB400] Slow Query Performance from the Web
>
> If you can put you app in debug and set a break point after
> it establishes a connection but before it runs the query, you
> can find the job the query will run under (use command
> NETSTAT *CNN, subset by the IP address of the machine running
> the code, then use option 8 to see the jobs for that
> connection), start a service job on it, and type STRDBG
> UPDPROD(*YES). This will cause the query optimizer to print
> debugging information in it's job log when the query runs. If
> you can't but it in debug and set a breakpoint, there's a
> setting you can change in QAQQINI to do the same thing (I
> don't know what the setting is but that should be easy for
> you to find out).
>
> Matt

Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.