Re: SQL/T or maybe it's SQL T?
- From: Denis <denis.sun@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Fri, 20 May 2011 13:41:04 -0700 (PDT)
The only time I have to use SQLT is per Oracle support request. I guess because
SQLT output is in HTML and including everthing like execution plan, stats etc,
it is easy for them to check. Like in the case that they like RDA ( I admit I
gave them RDA but myself never look into it). Other than that, not much
of use.
Simply checking execution plan, and tables, columns, indexes stats and at most
10053 trace will do the job.
Usually I can find problem SQL from database itself, v$sqlarea or statspack/awr
top sql section, not neccessarily from dev. Acutally most of time dev in my
site
has no idea how their sqls work.
BTW, you need to install sqlt package in your database.
Denis
From:oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Sandra Becker
Sent: Friday, May 20, 2011 4:00 PM
To: Taylor, Chris David
Cc: aprilcsims@xxxxxxxxx; oracle-l
Subject: Re: SQL/T or maybe it's SQL T?
The customer DBA seems to think this is a new tool. Whatever. If it can give
me any additional information in tuning poorly performing queries, I'm open to
looking at it. The biggest problem I have is that no one on our development
team has supplied me with the problem queries yet. How do you tune what you
don't have? I'm asking again for the information and now that an influential
customer also is asking, maybe I'll get it this time.
Sandy
.
Other related posts:
