RE: full-scan vs index for "small" tables
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 28 Jun 2006 16:50:35 -0000
>Mark J. Bobak
>Cases like the above are where the optimizer can go wrong. It simply
doesn't know enough about the data and it's distribution to make the
correct decision.
>On Behalf Of Cary Millsap
>My experience is that most problems that people think are category II
problems are really
> category I problems in disguise. The difference can be revealed by
inspection of 10053 data.
That kind of philosophy is exactly why I moved from developers to dba.
Why should I be fighting Oracle for developers salary when I can do it
for dba's?
More important, my chief was not happy at all to pay developers for
inspecting 10053 traces.
He happened to remember those days when correct table ordering in the
from-clause and a few hints in the extreme cases would have done the
job.
I understand that Oracle wants to have the same thing for OLTP and DW.
The engineering problem here is that cars are for driving and plains are
for flying. Let's hope no other vendor will solve this problem better.
Then I can save for reeducation and concentrate on solving
problems(inspecting 10053 traces for example) on Oracle platform.
Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--
//www.freelists.org/webpage/oracle-l
Other related posts:
