Skip to main content

The 2014 PL/SQL by Feuerstein Webinar Series


Now that I am settling in very nicely at Oracle Corporation, after a 22 year absence, it's time to get back to celebrating all the wonderful things you can do with PL/SQL, along with advice about how to best do those things.

I am happy to announce that Oracle Corporation and ODTUG are teaming up to co-host a six-month webinar series on the Oracle PL/SQL language.

The first three webinars, hosted by Oracle, will focus on PL/SQL best practices:
[My apologies about the late notice for the first webcast, scheduled for next week. Like I said: I just got settled in.]

The second set of three webinars, hosted by ODTUG, take on the challenge of mining the PL/SQL language for features and techniques to improve performance:
Whether you are new to PL/SQL or have some years under your belt, attending these six webinars will deepen your expertise and help you think in new and creative ways about how to write fast, maintainable applications.

All webcasts will be recorded and available for viewing 24 hours a day, 7 days a week, for as long as electricity powers the Internet.

I hope you can join me!

Steven

Comments

  1. iudithOctober 12, 2014 at 10:26 AM

    Hello Steven,

    Are there any news regarding the recording of the 3rd webinar, from Sep 17 ?
    The web page still says "will be available soon" ...

    Thanks a lot & Best Regards,
    Iudith

    ReplyDelete
  2. Steven FeuersteinOctober 12, 2014 at 9:12 PM

    Ah, thanks for the reminder, Iudith. I will get that done early this week.

    ReplyDelete
  3. iudithOctober 17, 2014 at 11:06 AM

    Hello Steven,

    Thanks a lot for the additions, I was lucky enough to be able to listen "live" to yesterday's webinar (happening to be at home), and I will be happy to follow after
    the next ones :) :)

    It would be great if I would be able to make a habit and listen (and re-listen)
    at work to the so many webinars available.

    If I think it over, then yes, the Internet is the one that most changed our lives,
    not even the computer alone ...
    If this was for good or for bad ? That is the biggest question to all of us :)

    Thanks a lot again & Best Regards,
    Iudith

    ReplyDelete
    Replies
    1. AnonymousJanuary 28, 2015 at 6:42 AM

      Hi Steven,

      Is there a way to view Ten (Other) Tips for Improving PL/SQL Performance? The link above says that the webinar has ended.

      Thanks,
      Karen

      Delete
    2. Steven FeuersteinJanuary 30, 2015 at 7:43 AM

      Karen, I will get that fixed by early next week. In the meantime, please do watch the video at:

      https://www.youtube.com/watch?v=EoyRxPxU26U

      Delete

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more