Re: full table scan performance

Hi Dean,

perhaps it's normal depending on the time parsing.

Analyze your query with tkprof (and init.ora parameter : timed_statitics on) to get the time of the parsing

Or to see if it's due to the parse, after executing twice (or more) your statement, then
change it a little like that to force a parse again :  select *
 from TABLE_1 where 1 = 1

Hope this help's

Regards. Olivier

dean_at_gfsmortgage.com wrote:

> I stumbled across something I've never encountered and was wondering if anyone
> had any suggestions. I'm sure it's a parameter matter, but I can't see it.
>
> While playing around with optimizing full table scans I noticed that if I did
> a
>
> select * from table_1
>
> from SQL Worksheet (locally on the server)
> It took 40 seconds to get all 8302 rows. If I hit F5 to execute it again, it
> took 1:20, hit F5 again and it took about 1:45. It seems to continue to get
> worse after that.
> I am the only one logged onto the server (an NT 4.0 SP3 Dell Poweredge 2300)
> and I only run the one query.
> If I close SQL Worksheet and reopen it, the same process continues (:40, 1:20,
> 1:45, etc.) This happens even if I cache the table via hints.
>
> Anyone know what I've screwed up?
> -Dean
Received on Tue Aug 18 1998 - 15:54:36 CDT