Re: Optimize Query with multiple joins
Thanks for the fast answer, glad to know that the query plan is as good as it can be.
Your guess was right, the "d.id" is the alias for "dest". I guess my benchmarking simply wasn't that good, I'll remove the distinct.
Also, I'm aware of the non order by clause. I think it wasn't added in the beggining for performance reasons, I'll add it now.
That said, where could I investigate further the reason of this query being slow under heavy load? Maybe it's a hardware limitation?
Thanks again!
Angel
Edited 1 time(s). Last edit at 03/24/2011 07:04AM by Angel Lacustre.
Subject
Views
Written By
Posted
10024
March 24, 2011 06:22AM
3524
March 24, 2011 06:53AM
Re: Optimize Query with multiple joins
2004
March 24, 2011 07:02AM
2540
March 25, 2011 07:46AM
2001
March 28, 2011 04:28AM
1966
March 28, 2011 11:05PM
1869
March 29, 2011 12:49AM
2056
March 29, 2011 08:28AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.