Re: Optimizing performance
From: Fernando Pereira <n_at_nowhere.com>
Date: 1997/05/15
Message-ID: <01bc60fe$342fd180$821c41c2_at_tubarao>#1/1
Date: 1997/05/15
Message-ID: <01bc60fe$342fd180$821c41c2_at_tubarao>#1/1
The main purpose of our tool TunaSQL is just to optimize Queries. You can go for a tour at our web site.
Warning: our present demo version will only work with the SCOTT tables, but we will change it soon.
-- Fernando (morgan_at_cardume.com) CardumeSoftware www.cardume.com Sheilah Scheurich <scheuric_at_sprynet.com> wrote in article <3370e626.19022449_at_news.interserv.com>...Received on Thu May 15 1997 - 00:00:00 CEST
> On 29 Apr 1997 10:10:00 GMT, "Luis Servan" <lservan_at_mx2.redestb.es>
> wrote:
>
> >I'd like to know how can I optimize the time response of database
queries
> >from applications developed with Designer/2000
> >
>
> One way to determine if the query is optimized, it to isolate either
> the session, or the query itself and run through TKPROF. This will
> tell you if you are using the proper index, if the sql is efficient,
> etc.. To islolate the query, use the stored procedure:
> EXECUTE DBMS_SYSTEM.SET_SQL_TRACE_IN_SESSION(A,B,TRUE);
>
> Where a is the sid (session id), and b is the serial number. This can
> be found in the v$session table.
>
> Sheilah Scheurich
> DBA
> scheuric_at_sprynet.com
>