Re: tune between query/join

  • From: Greg Rahn <greg@xxxxxxxxxxxxxxxxxx>
  • To: ax.mount@xxxxxxxxx
  • Date: Fri, 21 Oct 2011 14:18:41 -0700

I think this may be being approached in the wrong direction -- instead
of trying to "tune" the query, why not ask what is the business
question trying to be answered?
Once we have the biz question and the data format, the best way to get
to the answer can be discussed.

Exadata isn't going to solve a poorly written query that produces rows
unnecessarily.  Step 1 is to write SQL that works.

On Fri, Oct 21, 2011 at 7:09 AM, amonte <ax.mount@xxxxxxxxx> wrote:
> unfortunatey there arent any common columns, this is a pity really
> this is a data migration process and the guy who modelled this left the
> company :-(
>
> and yes, it reads million of rows even the entire tables are cached, I dont
> think this would work even with exadata
>
> let me get some test data...

-- 
Regards,
Greg Rahn
http://structureddata.org
--
//www.freelists.org/webpage/oracle-l


Other related posts: