Fwd: Big SQLs
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: oracle-l-freelists <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 19 Apr 2009 19:41:15 +0100
missed the list off in case this advice looks like garbage.
---------- Forwarded message ----------
From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
Date: Sun, Apr 19, 2009 at 7:40 PM
Subject: Re: Big SQLs
To: lambu999@xxxxxxxxx
In addition to the other two comments I tend to find that the select list is
rather long and can be somewhat ruthlessly culled when trying to understand.
A good sql formatter really helps - sqldeveloper now has one for example -
and that where code is generated it can be somewhat helpful to view what the
developer/report writer is doing in the calling program.
Niall
On Sun, Apr 19, 2009 at 8:09 AM, Ram K <lambu999@xxxxxxxxx> wrote:
> Hi
>
> I ran into a big SQL that was several pages yesterday. Are there any
> strategies and tips to understand first and then later tune such SQLs. I
> realize this is a broad question. One approach I can think of is divide and
> conquer.
>
> Ram.
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
Other related posts:
- » Fwd: Big SQLs - Niall Litchfield
