Insights into Statistics, Query Optimization and the Oracle Optimizer

Oracle OpenWorld 2012

Maria Colgan
Distinguished Product Manager

I can't believe it's time for OpenWorld again!

Oracle OpenWorld is the largest gathering of Oracle customers, partners, developers, and technology enthusiasts. This year it will take place between September 30th and October 4th in San Francisco. Of course, the Optimizer development group will be there and you will have multiple opportunities to meet the team, in one of our technical sessions, or at the Oracle Database demogrounds.

This year the Optimizer team has 2 technical sessions, as well as a booth in the Oracle Database demogrounds.

  • Tuesday, October 2nd at 1:15pm Oracle Optimizer: Harnessing the Power of Optimizer Hints
    Session CON8455 at Moscone South - room 103
    In this session we will discuss in detail how optimizer hints are interpreted, when they should be used, and why they sometimes appear to be ignored.
  • Thursday, October 4th at 12:45pm Oracle Optimizer: An Insider’s View of How the Optimizer Works
    Session CON8457 at Moscone South - room 104
    This session explains how the latest version of the optimizer works and the best ways you can influence its decisions to ensure you get optimal execution every time. It will also include a full history of the Cost Based Optimizer, so make sure you stick around for this one!

If you have burning Optimizer or statistics related questions, or if you just want to pick up an Optimizer bumper sticker, you can stop by the Optimizer demo booth. This year we are located in booth 3157, in the Database area of the demogrounds, in Moscone South. Members of the Optimizer development team will be there Monday through Wednesday from 9:45 am until 6pm.

The full Oracle OpenWorld catalog is on-line, or you can browse by speakers by name. So start planning your trip today!

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.