A few days ago, I did a short post about the start of the Miracle Scotland Database Forum 2007. I decided to wait until getting back home to complete a full-blown description of the event. I should warn you, this will be quite lengthy, so draw a deep breath.
A short post to draw your attention to this article by Kevin Burton titled “MySQL and the Death of Raid”. Although it’s written from the MySQL point of view, he does bring up some interesting points on the advantages of what he calls a “RAISe” or Redundant Array of Independent Servers” architecture (actually I coined the RAISe acronym just now :-) ) over the traditional RAID approach of hardening the availability and performance of your disk. Take a look and let me know what you think.
Ronald Bradford has published the 47th edition of Log Buffer, the weekly review of database blogs, on Technical Notes and Articles of Interest.
So you have followed the recipes to create a standby database, setup the database to switch logs automatically, and now, as with any good database, the space required to support the application grows and grows and grows. Eventually, using your monitoring software (in my case, Pythian’s avail or dailies), you get an alert suggesting that you will need to add additional space. In this case you are going to add a datafile to a tablespace, or add a brand new tablespace.
Yesterday was the opening and I should say it was great — nice tour on the Whiskey Heritage Center and couple interesting and humorous sessions delivered by Jonathan Lewis and Graham Wood combined with whiskey tasting. The evening obviously continued after that but you can assume that anyway if you know what I’m talking about.
If you are following my blog then you might recall that I’m going to make a presentation on the Miracle Scotland Database Forum 2007. My presentation is called RAC load testing adventures and it’s based on a project I’ve been through with one of our clients.
Welcome to the 46th edition of Log Buffer, the weekly review of database blogs.
With this post, I’m starting a series about Oracle Block Change Tracking internals. The feature was introduced in Oracle 10 Release 1. I have already published my past presentations and the white paper about that. When I first started, I tried to dig at least something from Metalink, but the public notes contained no implementation details. What I extracted is some pieces of bug texts, and from there I concluded that fixed tables starting with X$KRC are most probably related to the BCT feature.
I’ve just added 6 reports about RAC in the SQL*Developer Plug-In.
With the help of an anonymous friend, I’ve made available a new SQL*Developer Plug-In.