Back in March of last year I wrote an article on the five frequently misused metrics in Oracle: These Aren’t the Metrics You’re Looking For.
To sum up, my five picks for the most misused metrics were:
We’ve all got problems. More to the point, every IT department or team has problems of some kind. It’s why we hire consultants, buy products, start long and arduous journeys into the great unknown depths of root cause analysis, and so on.
What fascinates me is the level at which we come to identify with our problems. When I’ve gone into an environment to deliver recommendations, the conversation usually goes something like this:
Alchemists are best known for their (completely fictional and entirely ridiculous, but that’s besides the point) amazing ability to turn lead into gold. Let’s face it, there’s a lot of lead in the Oracle world. Bugs, angry developers, metrics that can seem to elude human understanding…but I digress.
You’ve purchased servers, storage space, switches, cables, and countless other pieces of hardware. The Oracle licenses are bought and paid for, Enterprise Edition with a few add-ons. All told, you’ve spent a small fortune on this infrastructure. It’s finally time to start up your database and begin using it for projects…
…Data gathers, and now your cost begins.
DBAs and other IT professionals (and sometimes naive executives) can fall into the trap of thinking that the up front costs of application building are all you have to consider for an application. To be honest, a lot of IT professionals don’t even think that far–we need components, we buy them. But the costs pile up far beyond the initial purchase.
Thank you all who attended my sessions at NYOUG Fall Conference this morning. I appreciate spending you most precious commodity - your time - with me. I sincerely hope you found both the presentations enlightening as well as entertaining.
Please see the details of the sessions below along with the download links.
Yet another Oracle version is out and so are about 1500 new features in a variety of areas. Some are well marketed (e.g. pluggable database or the multitenant option) and some shine by their sheer usefulness. And there are some that do not get a whole lot of coverage but are are hidden gems. In this session you learned 12 broad areas of Oracle Database 12c I feel are worth learning about to make your job as a DBA or developer better, easier, smoother and, in some cases, even make it possible what was hitherto impossible or impractical.
I just wanted to put up a post about DBMS_APPLICATION_INFO. This is a fantastic little built-in PL/SQL package that Oracle has provided since Oracle 8 to allow you to instrument your code. i.e record what it is doing. I’m a big fan of DBMS_APPLICATION_INFO and have used it several times to help identify where in an application time is being spent and how that pattern of time has altered.
Some PL/SQL developers use it and some don’t. It seems to me that it’s use comes down to where you work, as most PL/SQL developers are aware of it – but not everyone uses it (a friend of mine made the comment recently that “all good PL/SQL developers use it“. I can understand his point but don’t 100% agree).