Re: Performance advice

Serge Rielau <srielau@ca.eye-be-em.com> writes: > As an SQL Person I want to point out though that when you tune the > design and the SQL first then you tune the engine to teh right design. > If you do it the other way around you have tunes the goo and have to > redo it when you tune the SQL. What he said. It's always more cost effective to tune a badly performing SQL query first. An order of magnitude gain in software is waaaaay cheaper than paying for an order of magnitude gain in hardware! -- Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412 Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142 President, CEO Fax: (760) 499-9152 My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B

Ronald Cole wrote: > > What he said. It's always more cost effective to tune a badly > performing SQL query first. An order of magnitude gain in software is > waaaaay cheaper than paying for an order of magnitude gain in > hardware! Who said anything about paying for more hardware? Getting the engine sorted is the easiest job, and can yield upto several times improvements. Getting a new engine configured correctly should be routine, and it's always a suitable first step.