tag:blogger.com,1999:blog-25740336.post5915750714858536980..comments2007-12-13T08:22:58.727ZDavid Kurtzhttp://www.blogger.com/profile/08139761793598085235noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-25740336.post-62650744319311407172007-12-13T01:22:00.000Z2007-12-13T01:22:00.000ZYou touch on a very valid point here, David. <BR/><BR/>I can understand the concept of increasing the "smartness" of the optimizer and Oracle's efforts in this area. <BR/><BR/>But there is such a thing as "too smart", for lack of a better expression.<BR/><BR/>One thing that steady state production environments do NOT need is ad-hoc change. Guess what the so-called "smart optimizer" means?<BR/><BR/><BR/>Is it desirable in the long run? All I can say is: as much as possible, I try to turn off all this smartness so that I can end up with a predictable system. It might not run as fast as it could in some cases, but it sure ain't gonna blow up in execution times without telling me!Noonshttp://www.blogger.com/profile/07694829378563989648noreply@blogger.com