Re: Comparing Top 5 Timed Events and Cache Advisory

From: Mladen Gogala <>
Date: Sun, 19 Jun 2011 18:06:06 +0000 (UTC)
Message-ID: <>

On Sun, 19 Jun 2011 23:08:22 +1000, Noons wrote:
>> Love that stuff. Indexes are slow? Where are they moving to?

> LOL! Amazing how these things start, isn't it? A bunch of partitioned
> tables make a few batch jobs run faster when using only the partition
> key or a local prefixed index and all of a sudden, "all" indexes are
> slow! :D

Several years ago, one gentleman, that happened to be an end user of an application that was accessing an Oracle instance, reported me to HR. The event that he was complaining about was the following: he called the IT, DBA service and complained that the database is slow today. It was me who picked up and explained to him that the databases without users or data never create problems for anyone and that it's all his fault. The HR person who was adjudicating the complaint didn't like the guy, so nothing really happened. However, I still do receive calls and complaints from people complaining that the "database is slow". The "database" is somewhat vaguely defined term, like "the Force" from the Star Wars movies. Being my usual self, I now get people to admit that the application is what is being slow, because they don't have access to the database in the first place. With an appropriate dose of humor, you can train the end users to tell you that when they press "Submit" button in the window for ***, they are waiting for * minutes. That's something I can work with. If the user tells me that the database is slow or that indexes are slow, he's practically guaranteed to have a Black Adder like conversation with me, with him being treated as Baldrick. I love the smell of napalm in the morning.

Received on Sun Jun 19 2011 - 13:06:06 CDT

Original text of this message