6 responses

  1. Martin Berger
    July 5, 2011

    The first time I read about Edition based Redefinition my first idea was:
    They must do this in any Data Dictionary modification!all Objects in the data dictionary exposed to the customer (as far as I know) can be handled that way. So I really hope for no need for a Service downtime anymore. at all. never, ever! even with ORA-600 and emergency patches.
    Of course, there are other ideas too:
    * in my company, we see the total automatism on parallel queries is not perfect, yet.
    * in rare cases I’d like to be able to store a SQL (for a particular user) into the DB to avoid any kind of hard/soft parsing, permission checks, object checks, … maybe even in PGA?
    * currently I’d like to have a COMMIT_WAIT=nowait hint.
    So there are enough wishes, let’s see what Larry will bring to us.

    • JeffS
      JeffS
      July 5, 2011

      Avoid permission checks? What do you mean by saving a SQL? Don’t we call this a ‘VIEW’?

    • Gary
      July 5, 2011

      A stored procedure comes close to minimising the syntax /semantics checks. And PL/SQL cursor caching means not even soft parses for repeated SQL. The problem is (a) the soft parse is needed for any parse coming through from the client to see whether the text matches an existing SQL and (b) ‘new’ developers don’t want to handle low level stuff like cursor handles or take advantage of code in the DB.

      Think its too early for a 12g though. But what I’d REALLY like to see is Oracle Personal Edition for Linux not just Windows.

      • JeffS
        JeffS
        July 5, 2011

        No ones talking about it, so if I’m right, I’m a genius! An evil genius.

        Gary, your answer to every question is PL/SQL – I like that!

  2. Martin Berger
    July 6, 2011

    Jeff,
    I just want to avoid all the boring parsing steps for heavy used statements.
    Instead of SELECT SYSDATE FROM DUAL WHERE DUMMY=:1 something like
    DO PREPARED STATEMENT ‘sqlid’, :1 Less CPU burned, less latches, …
    Garys example is right with PL/SQL, and cursor caching. I’d just want to bring this idea to the end.

    • JeffS
      JeffS
      July 6, 2011

      Never thought of that parsing as that taxing, although if it’s happening a few thousand times a minute, I suppose those milliseconds add up.

      Have you taken advantage of the result set cache and deterministic functions yet? I wonder if that would help any…parse is there, but less time spent elsewhere.

Leave a Reply

 

 

 

Back to top
mobile desktop