RE: rm RULE based optimizer != GOOD IDEA

  • From: "Post, Ethan" <Ethan.Post@xxxxxx>
  • To: <gints.plivna@xxxxxxxxx>, <robyn.sands@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Mon, 25 Apr 2005 08:16:52 -0500

or..."one of our developers used HASH JOIN hints all throughout their
SQL, now we had to go back and remove them and this took time and $$$,
can't wait until HASH JOIN hint is removed."

you see the problem in this case and the case below has to do with the
review process, not the mere existence of the hint

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Gints Plivna
Sent: Monday, April 25, 2005 3:41 AM
To: robyn.sands@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: rm RULE based optimizer !=3D GOOD IDEA

One of our developers used RULE hint widely in our latest project. As
a result we had to inspect almost all of them (taking time and $$$)
when moving to production. So from now I'm planning to allow RULE then
and only then if developer can explain _ALL_ RBO rules :)))

As a result I hope that those who will be able to do that would
understand that it is a  bad idea.



Other related posts: