Exadata and OLTP

When Oracle teamed with HP to introduce the first version of Exadata, the new product was positioned more as data warehouse appliance. In its second incarnation, Exadata (or rather, the Sun Oracle Database Machine – Exadata is really the storage component of the machine), Oracle has dramatically upped the ante – it’s now promoting  as a solution for OLTP (online transaction processing) as well.

For customers who are wondering if Exadata is for them, the way to decide is simple: if you have a large production database with tens of Terabytes of data, do consider Exadata – it probably will make a lot of sense, when you compare its cost with the improvement in performance, due to the Flash Cache feature and a brand new SQL processing strategy wherein most of the unnecessary data for a query is weeded out at the storage level.  If you have an OLTP database, you may want to consider Exadata  even if your database isn’t very large – Exadata supports extreme levels of transactions per second (TPS), even if you buy but a quarter rack, the smallest size in which Oracle sells Exadata.

Field reports have just started trickling in about production implementations and they indicate that the actual performance does match the promises.  The much wider data I/O  “pipes” made possible by Infiniband and the fact that you can continue to use all of Oracle’s industry leading database capabilities (partitioning, parallel processing etc) with Exadata mean only one thing: contenders such as Teradata and Netezza better watch out!

1 Comment » for Exadata and OLTP
  1. Rashmi says:

    Hi Sam,
    I am working on building up a case study where in I need to showcase how exadata will benefit thier OLTP (Ebusiness suite to be more precise).

    Do you have any kind of comaparitive statistics for the same?
    I understand that there will be benefits in terms of space and performance, but is there any way to compre the same?
    The current database is 11gR1.

    Kindly advise.

Leave a Reply

Your email address will not be published. Required fields are marked *