Re: Speed enhancements - one select, nested select, two consecuti ve s elects

[Kathy Anderson <AndersoK@ROTARYINTL.ORG>]

It's always a tough call to know what might be the fastest approach - it
depends on many factors:  your DB Platform (some handle nested selects
better than others), table size makes a difference, maybe one of the tables
you're hitting could use another index.  Depending on what you're trying to
do you might consider using a lookup table (use the load-lookup command to
create and load, use the lookup command to retrieve).   If the tables you're
going after are huge and your report includes detail from a small subset of
info from those tables you might consider creating a "reporting/summary"
table - of course this would require writing a process that loads the
summary table on a regular basis.

> -----Original Message-----
> From: Brown, Bryan [SMTP:bbrown2@ACSALASKA.COM]
> Sent: 15 May 2000 11:29 AM
> To:   SQR-USERS@list.iex.net
> Subject:      Speed enhancements - one select, nested select, two
> consecutive s elects
>
> Good morning everyone!
>
> Thanks to everyone's help, I managed to get my last report off the ground
> finally - Thanks!
>
> On a different report, I have an extremely slow report. I was wondering
> about performance of SQRs - which is the faster approach....
>
> 1.) A select with Joined tables
> 2.) Nested Select (i.e. select a from b where b = (select c from....)
> 3.) Two select statements:
>    a.) Select a from table1
>    b.) Select b from table 2 where c=a.table1
>
> Thanks,
> Bryan
>
> ------------------------------------------------------------
> Bryan E. Brown
> bbrown2@acsalaska.com, 907-564-1303
> Systems Analyst, ACS (Alaska Communication Systems)
> SQRW  V3.0.13.2, CSS Hrizon ver 8, Oracle 7.3.3, NT (server &
> workstations)