ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

Two questions about the Oracle in-memory database

Two questions about the Oracle in-memory database, announced in Sep. 2013, re-announced now, and coming… sometime later:

  1. Why would the performance improvement be visible only a specific hardware?

    Ellison said users can expect real-time analytics queries 100 times faster and online transaction processing that is two times faster as long as they are using hardware that supports the Oracle 12c database.

    I’ll assume that this could only mean that these results will be seen when data fits in memory. And not that one will need custom hardware to enable this feature. As a side note, I’m not sure I’m reading the announcement correctly, but it looks like a paying Oracle database customer will have to pay extra for the in-memory option.

  2. Can anyone explain how data can be stored both in columnar and row format?

    Additionally, the software will allow people to store data in both columns (used for analytics) and rows (used for transactions) as opposed to only one method; Ellison described this function as being “the magic of Oracle.”

    Magic has very little to do with databases and performance.

Original title and link: Two questions about the Oracle in-memory database (NoSQL database©myNoSQL)