Updated September 26, 2019


Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with SAP HANA

We currently use SAP HANA as a relational database. It is being used by the whole organization and is the database platform for six of our seven SAP systems. Since we have upgraded to the latest versions of ECC, CRM, and BW, we determined that a HANA database would best suite our needs.
  • Data retrieval has been quicker since it is a column-based database versus row-based database.
  • Applying HANA patches is easy (just download the patch and apply to Linux server.
  • Installing and setting up a HANA database is easier than other RDBMS systems.
  • We are currently using HANA 1.0 and the cascading replication is a little painful if you have more than one failover system.
  • Having to log in as that user to grant access to the schema is a little time-consuming. An ID that has system access should be able to grant access to any schema.
  • A nice feature to have is to be able to see activity at the DB level for users in the system versus all activity coming across as the SAP ID.
  • HANA is included in our global licensing since we have other SAP systems.
  • When doing upgrades, SAP HANA can be included when we do Support Pack and kernel upgrades. This saves time for the Basis team.
If we did not use SAP HANA, we would have used an Oracle 12c database. We selected HANA since it was recommended for Suite on HANA. So far SAP HANA has proven to be a great fit for our systems that are on Suite on HANA. All future systems we implement will be on SAP HANA.
SAP HANA is well suited for a company if you are installing or upgrading to Suite on HANA on later. This goes for the various SAP systems (ECC, CRM, PO, Solution Manager, Enterprise Portal, etc). Although SAP HANA could be used for non-SAP systems, I would use other relational databases for non-SAP systems.