Skip to main content

Meet (See) the Oracle Database Evangelist Team

We are all out at Oracle Headquarters for meetings this week and yesterday at the BIWA Summit, I was fortunate enough to:

  • Do a YesSQL presentation for the NoCOUG user group.
  • Have Tom Kyte share his thoughts on NoSQL -> SQL -> Not Only SQL -> Maybe SQL -> NewSQL -> YesSQL!
  • Enjoy 30 minutes of stories from Andy Mendelsohn, Executive Vice President, Server Technologies (most notably, Oracle Database).
  • Introduce the evangelist team.
We will publish a video of the session ASAP. Andy wowed the crowd with both thoughts on Oracle history and the current state of relational database technology. 

Bryn Llewellyn, PL/SQL Product Manager, was in the audience and took a nice shot of my team as offered quick introductions.



From right to left:
  • Todd Trichler - Community Manager
  • Natalka Roshak - SQL evangelist
  • Chris Saxon - SQL evangelist
  • Dan McGhan - Javascript/HTML5 evangelist
  • Steven Feuerstein - I forget what he focuses on. Oh, right: PL/SQL
Bryn also offered the following hilarious commentary:

Todd explains the evangelist's stance for an enthralled NoCOUG audience, and Chris demonstrates:

Eyes forward, shoulders back, and hands physically (and who knows, metaphorically too) covering the nether regions. Steven pulls his trousers up, eager to join in. But Dan is not yet convinced. Natalka is captivated by the delivery but bemused by the content.

Comments

  1. iudithJanuary 28, 2015 at 8:24 AM

    Hello Steven, All,

    Lots of luck to your entire team, in the benefit of the Oracle community and
    of all those who would like to see technology as a tool for making a better world
    on this planet :) :)

    And, if I am allowed to ask for it in the name of us all, please don't forget to ALWAYS consider your entire world-wide PL/SQL Challenge community members as
    "the 6-th silent Evangelist of your team" :):)

    We are always here, even if not always seen or heared :)

    Thanks a lot & Best Regards,
    Iudith Mentzel

    ReplyDelete
  2. Steven FeuersteinJanuary 28, 2015 at 8:52 AM

    Thanks for that reminder: 6th member. But I very much plan for you all not to be SILENT!

    ReplyDelete
  3. FahdJanuary 30, 2015 at 11:17 PM

    Steven looking Smart.

    ReplyDelete

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