Skip to main content

Results of the Oracle Dev Gym PL/SQL Challenge Championship for 2018

You will find below the rankings for the PL/SQL Challenge Championship for quizzes taken in 2018. The number next to the player's name is the number of times that player has participated in a championship. Below the table of results for this championship, you will find another list showing the championship history of each of these players.

Congratulations first and foremost to our top-ranked players:

1st Place: mentzel.iudith
2nd Place: Andrey Zaytsev
3rd Place: Tony Winn

Next, congratulations to everyone who played in the championship. We hope you found it entertaining, challenging and educational. And for those who were not able to participate in the championship, you can take the quizzes through the Practice feature. We will also make the championship as a whole available as a Test, so you can take it just like these players did.

Finally, many thanks and our deepest gratitude to our reviewers, especially Elic, who has once again performed an invaluable service to our community.

Rank Name Total Time % Correct Total Score
1 mentzel.iudith (5) 33 m 96% 3467
2 Andrey Zaytsev (5) 32 m 93% 3370
3 Tony Winn (3) 26 m 89% 3193
4 Ivan Blanarik (5) 33 m 86% 3116
5 Karel_Prech (5) 34 m 86% 3062
6 NielsHecker (5) 40 m 86% 3038
7 JeroenR (4) 35 m 86% 3010
8 Chase Mei (5) 24 m 82% 2951
9 MarcusM (3) 32 m 82% 2920
10 Oleksiy Ponomarenko (3) 25 m 82% 2897
11 mcelaya (4) 38 m 82% 2845
12 Maxim Borunov (5) 36 m 75% 2754
13 Jan Šerák (5) 40 m 75% 2689
14 Stelios Vlasopoulos (5) 44 m 79% 2674
15 Aleksei Davletiarov (1) 44 m 75% 2673
16 Rimantas Adomauskas (3) 33 m 75% 2666
17 seanm95 (5) 29 m 71% 2582
18 Mike Tessier (3) 33 m 71% 2567
19 siimkask (5) 18 m 71% 2525
20 Henry_A (5) 18 m 64% 2475
21 Rakesh Dadhich (5) 21 m 64% 2364
22 NickL (3) 31 m 64% 2324
23 Talebian (4) 34 m 64% 2314
24 Köteles Zsolt (1) 39 m 64% 2294
25 Otto Palenicek (3) 44 m 64% 2270
26 msonkoly (4) 44 m 61% 2171
27 Sachi (3) 10 m 61% 2108
28 RalfK (1) 13 m 54% 2045
29 PZOL (4) 30 m 57% 2027
30 richdellheim (1) 42 m 61% 1979
31 Sartograph (2) 30 m 61% 1976

Championship Performance History

After each name, the quarter in which he or she played, and the ranking in that championship.

Name History
mentzel.iudith 2014:1st, 2015:2nd, 2016:18th, 2017:2nd, 2018:1st
Andrey Zaytsev 2014:2nd, 2015:5th, 2016:1st, 2017:21st, 2018:2nd
Tony Winn 2016:2nd, 2018:3rd
Ivan Blanarik 2014:16th, 2015:16th, 2017:17th, 2018:4th
Karel_Prech 2014:4th, 2015:6th, 2016:11th, 2017:9th, 2018:5th
NielsHecker 2014:21st, 2015:1st, 2016:15th, 2017:3rd, 2018:6th
JeroenR 2014:7th, 2015:20th, 2016:6th, 2018:7th
Chase Mei 2014:25th, 2015:26th, 2016:3rd, 2017:20th, 2018:8th
MarcusM 2014:17th, 2015:37th, 2018:9th
Oleksiy Ponomarenko 2016:10th, 2017:4th, 2018:10th
mcelaya 2015:38th, 2016:34th, 2017:29th, 2018:11th
Maxim Borunov 2015:9th, 2016:17th, 2017:8th, 2018:12th
Jan Šerák 2014:24th, 2015:8th, 2016:7th, 2017:22nd, 2018:13th
Stelios Vlasopoulos 2014:37th, 2015:19th, 2016:24th, 2017:5th, 2018:14th
Aleksei Davletiarov 2018:15th
Rimantas Adomauskas 2017:6th, 2018:16th
seanm95 2014:34th, 2015:4th, 2016:9th, 2017:18th, 2018:17th
Mike Tessier 2017:33rd, 2018:18th
siimkask 2014:15th, 2015:14th, 2016:13th, 2017:12th, 2018:19th
Henry_A 2014:32nd, 2016:33rd, 2017:11th, 2018:20th
Rakesh Dadhich 2014:29th, 2015:31st, 2016:35th, 2017:31st, 2018:21st
NickL 2015:21st, 2018:22nd
Talebian 2015:23rd, 2018:23rd
Köteles Zsolt 2018:24th
Otto Palenicek 2016:29th, 2017:28th, 2018:25th
msonkoly 2015:15th, 2017:13th, 2018:26th
Sachi 2015:30th, 2016:28th, 2018:27th
RalfK 2018:28th
PZOL 2015:35th, 2017:23rd, 2018:29th
richdellheim 2018:30th
Sartograph 2017:10th, 2018:31st
Labels:

Comments

Post a Comment

Popular posts from this blog

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...
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

Table Functions, Part 1: Introduction and Exploration

Please do feel encouraged to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done! Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs. So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into. Of course, I am not the first to do so. I encourage to check out the  documentation , as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall . Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latter part...
31 comments
Read more