Re: Options to speed up a 7 table join executed frequently.

  • From: Subodh Deshpande <deshpande.subodh@xxxxxxxxx>
  • To: Joel.Patterson@xxxxxxxxxxx
  • Date: Wed, 23 Mar 2011 20:06:42 +0530

it all depends actually, like is query is only column list or functions,
group functions, string functions, computational functions,
what are those tables meant for like are they transactions, history or
masters and how they relate with each other
do they have proper indexes, if there is varity of columns..
depending upon that, sub-queryes, inline views are other available options

and finally how you want to see query output..


On 23 March 2011 17:38, <Joel.Patterson@xxxxxxxxxxx> wrote:

>  A developer asked for suggestions to speed up a query in oracle
> Solaris 10, soon to be 11gr2.
> He comes in around 2 hours from now, and I have asked to see the query.
> However…., here is the background.
> The query is generated by hibernate….    The query is called  very
> frequently.   The underlying data in the tables changes constantly.
> The query joins around seven tables.
> I thought perhaps a seven table join would be to complicated for a
> materialized view.
> I figure a normal view doesn’t stop the execution of the query…
> I thought perhaps a stored procedure where the data could be gathered
> manually via cursors, and all tools available there.
> A temporary table… yet that doesn’t solve the problem either, and so many
> people generate the query...
> So, I’m looking for ideas, I am just in the beginning stage.
> P.S.  I will be out after today until Monday.
> Joel Patterson
> Database Administrator
> 904 727-2546


Other related posts: