Skip to main content

No More PL/SQL Obsession by Steven Feuerstein on ToadWorld

A month ago, I received this email:
Hi Steven, just to inform you that your "PL/SQL Obsession" page is out of work, http://www.toadworld.com/sf answers "Page Not Found"  Maybe Dell has blocked you?
So I thought I would post a note on my blog to clarify matters.

 For many years, Quest and then Dell "hosted" my online PL/SQL resources at http://www.toadworld.com/sf:

I had lots of fun with that page, and am especially grateful to Steve Hilker for helping me keep it current and useful for thousands of PL/SQL developers.

We came up with what I still feel is the best way to describe my relationship to PL/SQL:
PL/SQL Obsession

And for more than a year after I joined Oracle (in March 2014), Dell and I agreed that we should keep the PL/SQL Obsession site intact, with all of my content, even that which they did not own.

But all things - good or otherwise - must come to an end. It's confusing to have me working at Oracle but still seeming to be "at" Dell inside ToadWorld.

So we, ahem, refactored the PL/SQL Obsession page so that it continues to offer PL/SQL resources, but is not tied to me personally, and we turned back on the redirect from toadworld.com/SF, so that you will no longer see a Page Not Found error.


So the bottom line is that you will still find it handy to head over to toadworld.com/SF for PL/SQL resources, but you will find the most current reflection of my PL/SQL activities at:

PL/SQL Home Page - Best starting point
Practically Perfect PL/SQL - PL/SQL Videos
PL/SQL Challenge - PL/SQL Quizzes (and more)
My Books on PL/SQL - published by O'Reilly Media
Daily PL/SQL Tips on Twittter

And of course there are lots of other great resources for Oracle Database developers at:

PL/SQL and EBR Blog - by our distinguished product manager, Bryn Llewellyn
PL/SQL on OTN - with content and the very active discussion forum
ORACLE-BASE - by the irrepressible Tim Hall
oracle-developer.net - fantastic articles and scripts by Adrian Billington
PL/SQL Scripts on LiveSQL - 24x7 access to Oracle Database 12c + code library
Ask Tom - you can still ask, but questions are now answered by Chris Saxon and Connor McDonald of the Oracle Database Developer Advocates team

Comments

  1. AnonymousNovember 19, 2015 at 12:10 PM

    Obviously Larry and Michael need to merge to instantiate the optimal solution. Until then this seems best.

    ReplyDelete
  2. UnknownNovember 20, 2015 at 10:12 PM

    Thanx for the heads up Steve

    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: Save your source code to files

PL/SQL is a database programming language. This means that your source code is compiled into  and executed from within the Oracle Database. There are many fantastic consequences of this fact, many of which are explored in Bryn Llewellyn's Why Use PL/SQL? whitepaper. But this also can mean that developers see the database as the natural repository for the original source code , and this is a bad mistake to make. It's not the sort of mistake any JavaScript or Java or php developer would ever make, because that code is not compiled into the database (well, you can  compile Java into the database, but that's not where 99.99% of all Java code lives). But it's a mistake that apparently too many Oracle Database developers make. So here's the bottom line: Store each PL/SQL program unit in its own file . Use a source code control system to manage those files. Compile them into the database as needed for development and testing. In other words: you should never kee...
16 comments
Read more