Skip to main content

Oracle Database Developer Choice Awards: the voting has begun!


The Oracle Database Developer Choice Awards celebrate and recognize technical expertise and contributions in the Oracle Database community. As longtime and new users of Oracle Database move to the Cloud and take advantage of this exciting new architecture, community experts will play a critical role in helping them succeed.

Panels of (mostly) Oracle ACE judges have now selected their finalists, and the time for public voting has begun! From 15 September to 15 October, we call on all members of the Oracle Database developer community to check out the finalists for each of these categories and vote for those you think deserve worldwide recognition for their work.

You can vote for as many finalists as you like, but you can register only one vote per finalist (even those of us living in Chicago).

And if you would like to help us generate buzz for the awards program via Twitter and other social media platforms, please use the #odevchoice hashtag.

Congratulations to all our finalists! Even if you do not take home an award, making it onto this list is a substantial achievement in and of itself.

SQL Finalists
  • Stew Ashton
  • Justin Cave
  • Kim Berg Hansen
  • Sayan Malashinov
  • Emrah Mete
  • Matthias Rogel
  • Erik van Roon
  • Sean Stuber
PL/SQL Finalists
  • Patrick Barel
  • Adrian Billington
  • Morten Braten
  • Bill Coulam
  • Kim Berg Hansen
  • Sean Stuber
  • Roger Troller
Oracle REST Data Services Finalists
  • Dietmar Aust
  • Morten Braten
  • Dimitri Gielis
  • Anton Nielsen
  • Kiran Pawar
  • Tim St. Hilaire
Oracle Application Express Finalists 
  • Morten Braten
  • Karen Cannell
  • Jari Laine
  • Paul MacMillan
  • Kiran Pawar
  • Trent Schafer
  • Juergen Schuster
Database Design Finalists
  • Heli Helskyaho
  • Mark Hoxey
  • Michelle Kolbe
  • Rob Lockard
The winners of the Oracle Database Developer Choice Awards will be announced at the YesSQL! Celebration on 27 October, during Oracle OpenWorld 2015.



Comments

  1. AnonymousSeptember 16, 2015 at 6:33 AM

    Good luck to all finalists.

    ReplyDelete
  2. Stew AshtonSeptember 16, 2015 at 7:55 AM

    Steven,

    Can you explain the "down vote" phenomenon?

    Many of us had 0 points but 8 votes this morning (France time). Some think voters are voting finalists down but I wonder if it's not a technical issue in most cases.

    Strange to have a "down vote" option and to show a running tally.

    Anyway, off to "down vote" my nearest competitors - kidding!!!

    ReplyDelete
    Replies
    1. Sayan MalakshinovSeptember 16, 2015 at 2:21 PM

      At start it was quite easy to find out who downvoted - i saw all voters list and in their accounts we can see for whom they upvoted(system adds points for upvotes), and the system doesn't show downvotes in account info.

      Delete
  3. Steven FeuersteinSeptember 16, 2015 at 8:18 AM

    I don't know if I can explain it, Stew, except to say: I wish that it weren't possible to down vote. But we could not turn that off. I hope and fully expect that as the vote tallies accumulate, the relatively small number of down votes (caused perhaps by the most ardent supports of another finalist? Like our primary system, drawing out the most "extreme"(ly supportive) voters?) will be overwhelmed by the up votes.

    ReplyDelete
  4. Stew AshtonSeptember 16, 2015 at 8:26 AM

    Thanks, Steven. Hope it's all a big success.

    ReplyDelete
  5. Morten BratenSeptember 22, 2015 at 7:35 AM

    Steven, quick question: Is it okay to ask family, friends and coworkers (who might not have OTN logins already) to vote for me? I had a quick look in the official rules, but got lost in the legalese... :-)

    ReplyDelete
  6. Steven FeuersteinSeptember 22, 2015 at 7:47 AM

    Is it OK? Hmmm, well, first of all, if a member of your family or a friend or a co-worker is not a government employee, does live in Quebec or Italy, does not work for Oracle, was not an awards judge, they are eligible to vote. So no violation of the rule and it is OK from that regard.

    Is it OK to campaign for your award and ask your community, however you define it, to support you? Absolutely.

    Would it be wonderful if one person happened to be related distantly to Genghis Khan and therefore had "family" numbering in the millions (http://blogs.discovermagazine.com/gnxp/2010/08/1-in-200-men-direct-descendants-of-genghis-khan/#.VgFpWItXP6Q) and they all voted and thus this person won an award?

    Maybe not so wonderful.

    The objective of the awards program is to give to our Oracle Database Developer community, and to highlight the achievements of more of the leaders in that community.

    So far it is doing just that and we have overall high expectations for the impact of this awards program.

    Hope that helps.

    Congratulations, by the way, Morten, on your triple nomination!

    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