Re: Full table scans

From: Paul Brewer <paul_at_paul.brewers.org.uk>
Date: Tue, 6 May 2003 19:53:50 +0100
Message-ID: <3eb804e5_3@mk-nntp-1.news.uk.worldonline.com>

"Kalle" <kminerva_at_jippii.fi> wrote in message news:3EB79950.8CA5BA2F_at_jippii.fi...
> Hi all,
>
> how I am able to locate the worst possible sql-statements from sga..
>
> Merci Beaucoup...
>
> Kalle
>

IMHO, this is a good question, but the heading conflicts with the text.

Without doubt, the best way to start tuning an app is to look at the offensive SQL (and an easy way to generate offensive SQL is to install Business Objects, but that's another topic: Business Objects? The DBA agrees with the Business; he objects violently!)

Seriously though: yes, locate the bad SQL; but bear in mind that full table scans are not necessarily bad SQL. One thing that might warrant a look however, is FTS inside nested loops.

Just my 2p

Regards,
Paul

P.S. As for Business Objects, it's a matter of collaborating with the developers, so as to create a sensible universe, then Business Objects is fine. You can't just create universes in a vacuum; only God can do that <g> Received on Tue May 06 2003 - 13:53:50 CDT