I recently took a peek at this online, interactive history of Oracle Corporation. When I got to the year 2008, I was surprised to see no mention of the production release of Exadata–the HP Oracle Database Machine. The first release of Exadata occurred in September 2008.
Once I advanced to 2009, however, I found mention of Exadata but I also found a couple of errors:
Kevin Closson put out a post yesterday called Critical Analysis Meets Exadata, linking to two awesome videos. It’s well worth spending the time to watch these, even if (like me) you never get so much as a sniff of Exadata.
I was lucky enough to be one of several people asked to review these videos before they were released. I’m sure some of the performance gurus on the Oak Table had a lot to say, but of the several comments I fed back to Kevin, I would just like to post a couple here:
If you are trying to find out more in-depth information on how Exadata architecture really works, I’m offering this video presentation to offer some critical thinking on the matter. It is broken into two segments. I do recommend watching both.
There was a question in the twitter-sphere about whether using sequences (sequence.NEXTVAL) in your select query’s projection list would somehow disable smart scans happening?
The answer is no, sequence use with smart scans works just fine. The smart scan offloading applies to data retrieval row sources (and filtering) only and nothing else. So, what you have in the query’s projection list (the sequence use for example), does not directly affect the smart scan decision. Just like any other operations like sorting, grouping etc, do not have anything to do with smart scans and don’t disable their use. Smart scans are only related to data retrieval and any other operations do not affect them.
As an active member of the Oracle user community I really enjoy talking to delegates at user conferences and user group meetings. As such I was very lucky having had the opportunity to attend two of them recently. I have written about the OUGN spring conference in the post before this, and I also enjoyed the AIM meeting earlier in March.
One of the subjects that always seems to come up is Exadata. Many, many DBAs want to have Exadata experience, and if only to tick a box. Now Exadata means a significant investment, in other words not every company on the planet will have one. On the other hand it’s reasonably complex to administer, therefore recruiters and other HR personal are very interested in DBAs with “Exadata experience”. Now, the reason of this blog post is an open question to the readers: what do you consider as Exadata experience?
If you are not familiar with R, this is the description from the R site: R is a language and environment for statistical computing and graphics. I encountered R at the Erasmus university, where I am working on a project with DNA data which is put in an Oracle database (see: http://huvariome.erasmusmc.nl/ (It’s down at the moment)).