RE: rm RULE based optimizer != GOOD IDEA

I currently manage database source control for at least 50+ developers who are checking source in for 3 concurrent versions of a software application. The only way to maintain control of the situation is training and a ton of automated validation and reporting. So you would set up monitoring which would alert you to a situation in which a developer checked in anything with RULE string in it. When you get that they get an email asking for supporting evidence that this actually is the solution. A get emails for every code change that contains a link to review the diff as well as daily emails before each build which shows me all changes checked in with the last 24 hours. After a almost 2 years of this you would not believe the things I catch developers doing almost weekly and end up adding yet more logic to trap the error in the future.

-----Original Message-----

From: Robyn [mailto:robyn.sands_at_gmail.com]=20 Sent: Friday, April 22, 2005 12:36 PM
To: Post, Ethan
Cc: oracle-l_at_freelists.org
Subject: Re: rm RULE based optimizer !=3D GOOD IDEA

I agree that the valid reason for RBO to go is to remove the need for code maintenance, but it has become a crutch in some of our systems and because of that, I personally won't miss it. Never meant to imply that lazy developers justifies Oracle getting rid of it.

As for the baseline, I'd prefer to see traces on the original code and use it as baseline to compare changes throughout a tuning process. Of course I can do this on the queries I know about, but I'm not the only one moving stuff to production.

In your case, you mentioned gathering the type of info I like to see BEFORE adding the rule hint, and I'd throw a party if one of developers did that.

Robyn

--

http://www.freelists.org/webpage/oracle-l Received on Fri Apr 22 2005 - 13:51:25 CDT