A good introduction was published in database journal. Check it out below (the first reference). I also suggest looking at the oracle tuning manual if you are at a sufficiently advanced level (second reference). Finally, there's a good introductory FAQ at orafaq (which is published by the company itself).
In general, I would suggest looking for the bottleneck in the application you have, and then trying to analyze the queries and so on that affect that bottleneck. Gathering statistics during peak usage is also a good idea.
2007-01-13 19:06:29
·
answer #1
·
answered by Matthew F 1
·
0⤊
0⤋
For the later versions of Oracle, the best way to approach tuning is to use the built-in Oracle performance tuning reports that are available.
AWR (Automatic workload repository), ASH (active session history) and ADDM (automatic database diagnostic monitor) use internal statistics on both the system and object level to help point out where the database is spending its time and where any bottleneck are occurring.
Assuming that the underlying hardware and operating system are working properly, this is the best way to see inside the database and is a valuable time-saver for identifying problems.
2014-12-24 07:13:44
·
answer #2
·
answered by x 2
·
1⤊
0⤋
Once an action plan is developed, performance tuning will be performed on the agreed-upon highest priority remediation tasks as project scope and time permits. PTC’s proven tuning methodology starts with the development of a validation plan and documentation of expected results.
2014-09-10 06:30:35
·
answer #3
·
answered by Farhan 2
·
0⤊
0⤋
visit
http://www.amazon.com/Oracle-Performance-Tuning-Nutshell-Handbooks/dp/1565922379
gs
2007-01-14 17:25:30
·
answer #4
·
answered by sandeep k 5
·
0⤊
0⤋