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

About SAP HANA in Relative Terms

Curt Monash reports from his briefings with SAP:

SAP HANA has what sounds like a natural disk-based persistence strategy — logs, snapshots, and so on. SAP says that this is synchronous enough to give ACID compliance. For some hardware partners, those “disks” are actually Fusion I/O cards.

I rarely encounter such relative terms used to describe a database. Can I have a database that stores a good amount of my data at a superb speed using a bizarre cluster persistence strategy?

As a side note, according to what I’m reading around, SAP is betting a lot on HANA and sees in it the solution that will make SAP the second largest database vendor.

Original title and link: About SAP HANA in Relative Terms (NoSQL database©myNoSQL)

via: http://www.dbms2.com/2012/02/26/sap-hana-today/