With this particular client, I ran a SHOW STATUS, waited 100 seconds, and ran it again. Handler_read_first jumped by about 53. So I wrote down in my notes: first in the index…every other second. Lots of table scans? As soon as I wrote it down I said, “That’s a haiku!” I counted syllables, and it works, but only if you pronounce “Every” with 3 syllables.
It’s yet again time for Oracle’s critical patch update (CPUJAN2008). The update will be released on Tuesday January 15, and as of yet there are no details on exactly what vulnerabilities have been found.
I was blog-tagged by Doug Burns – in his post, I *hate* chain letters ….I hate them too, I literally never pass them on no matter what vile fate that condemns me to. But this one includes a chance to talk about myself without seeming too self-involved, and there wasn’t even a threat of eternal damnation if I don’t do it. So let’s proceed then! 8 things about me that aren’t common knowledge…
I try to do a decent job of advocating for caring about good backups and business continuity strategies in my 7 Deadly Habits article. But this one beats them all, have a look for yourself, it too funny.
The listing of Dynamic System Variables on the MySQL Reference Manual’s page is supposed to show those variables you can change on-the-fly. The link at the top of this post, links to the 4.1 version of the manual, just in case folks are thinking I’m using a newer manual version. Mind you, I have this problem with 5.0.45 as well as 4.1.20.
I’ve been told that using NOT EXISTS in (Oracle) SQL is a bad idea, and that a way to overcome this problem is to collect the non-matching rows with an OUTER JOIN. So I decided to check if it is true.
While perusing the Oracle 11g Data Pump documents recently, I noticed a new parameter that was introduced in Oracle 10g, but I had missed it there. The parameter is TABLE_EXISTS_ACTION, and it applies only to the Data Pump Import. Basically, this feature allows you to decide how to handle importing data if a table already exists. Let’s create a simple test case to demonstrate.
This week, Daniel Krook brings us the 78th edition of Log Buffer, the weekly review of database blogs.
Welcome to the 77th edition of Log Buffer, the weekly review of database blogs.
In the era of consolidation, storage has not been left out. The impact of backup on normal database activity . . . batch processing in one database impacting transactional processing — these are two real life examples of the consequences of storage consolidation known to almost every DBA. Virtualization puts a new twist in consolidation, but storage virtualization methods are very under-developed compared to computing resource virtualization. Storage QoS and storage virtualization must necessarily be very closely-related areas with a lot of overlap.