Re: Oracle optimization

[Andrew Chan <Andrew_Chan@MANULIFE.COM>]

There is a good SQL optimizer called SQL Expert.  It does more than just query
optimizer but scan through your whole progrma and making suggestion to improve
performance.  Currently, it supports Oracle and SQL server.

You can download a trial version form www.leccotech.com.




Regards.

Andrew Chan
HRMS/Enterprise Systems
Manulife Financial
NTM-E2
andrew_chan@manulife.com
Phone# (416) 926-5950
Fax#       (416) 926-6087
Pager#  (416) 329-3999





Priscilla Davis <prisdav@MITRE.ORG> on 03/10/2000 08:17:48 AM

Please respond to sqr-users@list.iex.net

To:   SQR-USERS@list.iex.net
cc:    (bcc: Andrew Chan/Investments/Manulife)
Subject:  Re: Oracle optimization




I've done this with the begin-setup section:

begin-SETUP
  ALTER SESSION SET OPTIMIZER_GOAL='RULE'
end-SETUP

Not sure that applies here, though...

> "Kothandaraman, Ram" wrote:
>
> To put SQL hints in your SQR select statement, put it in a separate
> line after the begin-select.
> that should work. I spent more than a hour figuring this out last
> week.
>
> good luck
> ram
>
>      ----------
>      From:   Mathur, Neeraj[SMTP:NMathur@HRBLOCK.COM]
>      Reply To:       sqr-users@list.iex.net
>      Sent:   Tuesday, March 07, 2000 8:38 PM
>      To:     SQR-USERS@list.iex.net
>      Subject:        Oracle optimization
>      Importance:     High
>
>      Hi all,
>
>      We have Oracle environment here. We have a report in which SQL is
>      taking
>      forever to run. Same SQL if we run in Infomaker (query tool) runs
>      in 3
>      minutes. Our DBA says that we should put  /*+  FIRST_ROWS */
>      after the
>      select, but it gives syntax error if I put it after begin-select.
>
>      Has anyone faced a situation like this? And how to place the  /*+
>
>      FIRST_ROWS */     after select.
>      -Neeraj
>
>      Scanned by InterScan VirusWall
>
> Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
> affiliate companies are not responsible for errors or omissions in
> this e-mail message. Any personal comments made in this e-mail do not
> reflect the views of Blue Cross Blue Shield of Florida, Inc.