This is not a manufacturer driven book. At the time the book was written, Gaja V. was not an employee of Oracle. Also, what the tuning guru's at Oracle have known and disseminated about tuning Oracle databases for the past several years, is not necessarily what you would find in popular tuning books, or in Oracle's classes, though that is changing.
As for 'honestly', you will be hard pressed to find any more 'honest' tuning advice than that found in 'Oracle Performance Tuning 101'. The methods found in there are endorsed by the likes of Cary Millsap, Anjo Kolk, Jonathan Lewis, Mogens Norgaard and many others. I believe that Cary Millsap wrote the forward, though I don't have the book in front of me right now. Jared On Sunday 27 October 2002 12:52, Knut Herzog wrote: > Or a less manufacturer driven book, > > The "bee" book, O'Reilly's Oracle Performance Tuning Guide has a lot of > good hints, maybe sometimes a little bit more honestly. > > Regards > > Knut > > > > -----Original Message----- > From: Tim Bunce [mailto:Tim.Bunce@;pobox.com] > Sent: Sunday, October 27, 2002 7:16 PM > To: Knut Herzog > Cc: 'Bharat'; [EMAIL PROTECTED] > Subject: Re: Oracle /Perl Access Speed Optimization > > > Oracle performance tuning made easy: > > Step 1: Buy this book... > > Oracle Performance Tuning 101 > By Gaja Krishna Vaidyanatha, John A. Kostelac, Kirtikumar Deshpande > Oracle Press, Paperback, Published June 2001, ISBN 0072131454 > > Step 2: Do what it says. > > Tim. > > p.s. Run a mile from anyone who says that cache hit ratios are a > good way to tune an oracle database. They're way out of date. > > On Sat, Oct 26, 2002 at 01:50:10AM -0700, Knut Herzog wrote: > > Bharat, > > > > first two important notices from Oracle tuning guides : > > > > "If you want to tune your database, don't do it" > > > > "If you want to increase performance, you have to find the bottleneck" > > > > Next a few hints where you can start tuning your database : > > > > use "explain plan"(see Oracle docs) to see wether your sql queries use > > indexes or do full table scans. If they do full table scans on large > > tables, create indexes for these fields. > > > > Find out, what queries cause the slowliness and try to tune sql. > > > > Switch on statistics in your database and analyze results. > > > > Set optimizer to Cost based. > > > > There's a lot more about Oracle tuning, but this should be enough to > > start. > > > > Knut > > > > -----Original Message----- > > From: Bharat [mailto:bgbadhe@;rediffmail.com] > > Sent: Saturday, October 26, 2002 8:56 AM > > To: [EMAIL PROTECTED] > > Subject: Oracle /Perl Access Speed Optimization > > > > > > > > Hi , > > > > I am using perl 5.6 with Oracle 8i on redhat Linux 7.2 > > system, Iam facing probelm in speed of processing records, > > I have around 30K records sets ( 1 record set means records > > from 30 table) now in the database > > (can go upto 80K) . > > my Existing program is taking 16 hrs to read these set and > > create an XML and / Excel file. > > I am preparing set of queries at the begining and executing it > > with parameters for every Record set. > > which returns array of hash references for all records per > > record set and then I am writing to either XML/Excel file. > > > > Can it be possible to reduce this processing time ? > > Also , Will stored procedure help in this case and how do I use > > it (pl mention sample code) ? > > > > > > > > Bharat > > > > > > > > Bharat Badhe
