SAP HANA Reviews

We always make use of the latest version. 

We like that SAP HANA is a new technology. We also like that the product is both vertically and horizontally scalable, allowing us to do around 86 percent compression of documentation from 50 to seven terabytes.

In light of the hosting cost, we find this to be very interesting. We also like the warm and cold data in respect of the solution's technology. There is a real team involved. The customer can initially utilize SAP ECC on the HANA interface and then go on S/4HANA. From this point on, doing upgrades will be very easy and smooth and the risk management will be extremely light.

Since only some accommodation exists, there is a need to enquire of SAP about which environment would be good. While I know the HANA database on the Azure environment comprises a good solution, for example, it does not easily accommodate SAP. HANA is a new technology which only dates back to 2004 and we must give it adequate time before assessing its room for improvement. This is in contrast to DB2, which has been  around for 40 years or more years. Perhaps the flow will be improved. As of now, the technology is too new to properly comment on.   

The documentation is not an issue and, if anything, a surfeit of it is made available. This is actually one of SAP's stronger points.

Capabilities are also not at issue at present. When it comes to how EAP connects with SAP we are looking at a revolutionary paradigm. For now, we could not ask for there to be more features. This area is wonderful. We find the solution to be very helpful, safe, good and secure. Only with the passage of time will we be afforded a proper understanding of where the technology can be improved. 

This said, it would be nice to know when SAP plans to stop its maintenance of a previous version of SAP ECC ERP because, at this point, anyone utilizing SAP will have no choice but to go on S/4HANA Database. This will be contingent on when SAP will stop doing maintenance for the ECC version 6.0. 

We saw this with the 4.6 version ECC. Once SAP stopped its maintenance those with SAP were forced to go on the new version. 

We have been using SAP HANA for a couple of years. 

The solution is secure and stable. 

As the solution allows for document compression, I would consider it scalable. 

We have had occasion to make use of technical support, although its level varies according to the locale of SAP's global presence. 

While I was not personally involved in the installation, my engineers were. 

My deployment and maintenance team comprises around seven people, although I could not tell you which percentage of this is made up of managers, administrators and engineers. 

A monthly or yearly license must be purchased, although its utility will be based on the cost-benefit analysis that is reached by the individual customer. 

The solution is cloud based

I would recommend S/4HANA to other users. 

I rate SAP HANA as a nine out of ten. 

We are system implementers and we have many clients who use SAP HANA. Some examples of our customers are factories, hospitals, and other businesses.

This is a feature-rich product and I like all of them.

The price of this product should be reduced.

Technical support should be more customer-friendly.

We would like to see better CRM functionality in the future because there are other products that are better and more effective.

I have been using SAP HANA since they first launched the HANA database, several years ago.

This is a stable solution.

SAP HANA is scalable and we have a lot of clients who use this product. We have installed it for perhaps 15,000 users, and plan to increase our client base.

The technical support from SAP is medium. I'm not fully satisfied and it could be improved.

It isn't always a matter of them needing to being faster. Sometimes they cannot answer our questions, whereas other times, the answers come so late that we have already solved the problem.

We used to implement our own product that we had developed. However, after engaging with SAP, we substituted our own product for SAP HANA.

The initial setup was straightforward.

We have a team of about 200 consultants who implement, deploy, and maintain solutions such as this one.

SAP HANA is an expensive product.

SAP HANA is a good product and I can recommend it.

I would rate this solution an eight out of ten.

The deployment model used was on-premises.

The most valuable feature is the unique style of this solution, on the performance side and then the data. 

The data storage requirement is reduced from the original database to the HANA database.

Previously the data takes 100% storage space, but when moved to HANA, the data was 70% to 75%. The data compression is very high.

If you are using SAP applications, HANA is suitable.

I think that the pricing is high and it needs improvement.

In the next release, they could separate the modules from the costing of the database. If they bundle it together with a new affordable price then customers will be ready to purchase it.

They need an affordable price to achieve most of the minimum requirement assets.

This solution is stable.

They keep upgrading to new versions and keep adding new add-ons to this solution. It is helpful to the customers who are ready to run HANA.

The initial setup is not complex to install. Anyone with Windows or a Mac would know the process.

The pricing is expensive and it should be broken into two products.

People who are technical will accept the cost, but financially they will assess whether this solution will bring them revenue or not. People often ask, how will I profit when the cost is so high?

If you value a good product and can afford it, then add it to the business.

I would rate this solution an eight out of ten.

We use this solution for database storage.

I am an SAP developer and consultant at my company. I examine the client's system and propose solutions that will ease their processes or make them faster. This involves programming, as well as other kinds of development.

We are using the on-premise deployment model.

This solution is very fast.

The backup solution and time machine should be more accurate, reliable, and comfortable to use. The inclusion of a well-performing Time Machine is vital.

If the interface were more comfortable and easy to use then it would be excellent. Sometimes, an incorrect request is taken to production and it will corruption everything in the production database.

When there are a large number of records to process in a transaction, it is not any faster than Oracle.

This solution is very stable. We have been using it for one year and there have been no problems with the database.

I was not involved in the setup of this solution. I only installed SAP HANA Express on my laptop, which was easy. The full version requires professional knowledge. It's not something you can install, like Microsoft Office, on any laptop.

We hired a consulting firm in Turkey to set up our solution. The two machines were configured by SAP Turkey.

I have more than nineteen years of experience with the Oracle database, from version 7.2 through to RAC. I know the administration, as well as backup and recovery very well.

There are not many differences between Oracle and HANA. As an example, for transactional purposes, it is very similar to Oracle.

We switched to HANA from Oracle because SAP systems are moving entirely to the HANA platform. There will be no support for SAP using Oracle.

We do not use the HANA features, for example, embedded scripts. This is something that we may use in the future.

My advice to anybody looking to implement a relational database is to use Oracle, rather than HANA. HANA consultants are very rare and therefore costly. My testing has also shown that Oracle in memory is much faster than HANA.

This is a good solution, but the vendor inaccurately promises that the database is ten-thousand times faster than Oracle.

I would rate this solution a seven out of ten.

We work with the latest update.

We use the solution as a database. We primarily use it for the SAP application. Some of the use cases involve CDS Views, which provides a quicker processing of the report and the application.

The in-memory database is a good and valuable feature.

Since we use BW, we are required to use an SLT tool to carry out the data for generating the reports. But, when it comes to in-memory database in respect of the realtime reporting, I do not see why this report cannot be made available from the system itself. This would allow for some partitioning of the database, so that there would not be a need for the EMP in respect of the realtime data.

The initial setup was complex. I am talking about how the data is replicated to the site. We had an Oracle Database and did replication to the VR site. Yet, when it comes to HANA, we are forced to work out the method for ensuring that this replication works as it should. It is at this point that the solution becomes stable. 

Technical support could be better. When we have requested this, the tendency has been to instruct us to implement a note and keep them apprised. In reality, there is no one who helps us with actual troubleshooting of the problem. 

The pricing is a bit on the high side. 

While I would definitely recommend the solution, I would caution that one should employ the proper resources that are geared towards the system. Unfortunately, SAP does not provide a structured training program, which means a person must rely on multiple system integrators and some service providers.

We have been using SAP HANA for more than three years.

The stability is very good and we have encountered no issues regarding it. 

The initial setup was complex. I am talking about how the data is replicated to the site. We had an Oracle Database and did replication to the VR site. Yet, when it comes to HANA, we are forced to work out the method for for ensuring that this replication works as it should. It is at this point that the solution becomes stable.

The solution is easy to scale.

Technical support could be better. When we have requested this, the tendency has been to instruct us to implement a note and keep them apprised. In reality, there is no one who helps us to actually troubleshoot the problem. 

We had already been using SAP when we switched from it to Oracle, because all of the innovations were taking place on HANA. 

The initial setup was complex. I am talking about how the data is replicated to the site. We had an Oracle database and did replication to the VR site. Yet, when it comes to HANA, we are forced to work out the method for for ensuring that this replication works as it should. It is at this point that the solution becomes stable.

The deployment lasted six months. 

We deployed with the help of a vendor.

No real maintenance is required. Data volume management is needed and all the reports are available, based on which the maintenance is easy. 

The pricing is a bit on the high side. 

The use of hardware does not incur additional costs. 

There are 40,000-plus users making use of the solution in our organization.

I rate SAP HANA as an eight out of ten. 

It is difficult for me to narrow down what the best features are in SAP HANA because they work together to provide the overall functionality of the solution. However, the Fiori application is very good.

In the Asian market, we have to customize SAP HANA to fit our needs and if we are implementing any solution from SAP or Oracle it is not recommended to customize them. 

In a future release, SAP HANA should add a module for taxation, such as income tax and withholding tax.

I have been using SAP HANA for a few months.

SAP HANA is highly stable.

We have not gone live yet with the solution to determine how many people with be using it. We have some applications deployed on our CRM and others will be deployed on SAP making it difficult to determine the potential usage of the solution at this time.

The price of SAP HANA is very expensive and it is paid annually.

I have evaluated other solutions from Oracle.

I would recommend this solution to others.

I rate SAP HANA a six out of ten.