SAP HANA Reviews

We are primarily using the solution for the BW system of SAP. We also use the legacy reporting, which is very good.

The solution is quite fast.

We hoped to move all our BI systems to work with HANA, unfortunately, there are a lot of performance issues, even after remodeling the BW models.

The memory is the solution's most valuable feature. It's the main feature of HANA. Others are still the regular IT databases that are on storage and are therefore much slower than HANA. The solution is quite fast.

Unlike other databases, it lacks management features that legacy databases like Oracle or SQL servers have. They need to make the solution easier to manage and offer tools that make management more effective. A lot of things you have on traditional databases you have to develop into HANA.

I've been using the solution for about 3 years

The solution is less stable than traditional databases. We have encountered several cases when the database just flows. For some reason, that database took a lot of memory, and when we opened a case with SAP, we had to send a lot of logs, which did nothing because at the end, they couldn't find the root cause for this issue. This happened in several cases. We had production down and that's not acceptable for our business.

The solution is very scalable. We have about 10,000 users.

Each of those is not connecting to the database per se, but we are using HANA to take all the data and a lot of users. Several other software applications are also connecting to it.

Technical support is okay, but not great. It seems like there are a lot of SAP support packages that are coming out and lots of versions. For me, this indicates that the product is not quite ready or stable enough.

We've contacted technical support in the past and did not get good results. Eventually, we just created some parameters that we have configured into the system. We solved the problem by ourselves by creating a workaround that avoided the problem. SAP never gave us a straight answer about what we should do in our case.

The initial setup was quite complicated. We had to do a migration, so it wasn't a fresh installation. We had Oracle as our legacy system and had to move everything over to HANA. We had to do half a year of testing and had to do several cycles of tests and migrations before deploying. Once that was done, we deployed over a weekend.

We handled the implementation ourselves.

We use the on-premises deployment model.

I'd advise others to wait until the software will be much more stable before implementing it.

I'd rate it eight out of ten. If it was more stable and more manageable, I'd rate it higher. If people could have the ability to do things on their own within the solution, to read the software logs on their own, and get the root cause of any problem, and not just send it to the support, it would be much better.

What is good about SAP HANA is its simplicity and its flexibility. 

Its in-memory capabilities are good, which is why many companies still use it. 

SAP HANA is a very proprietary tool and there's not as much support available for it as there is for an SQL Server (which is more popular). 

It requires some internal SAP knowledge to work with the tool and it's a completely graphical modeling kind of a system. You can't come in cold with no knowledge or understanding of the solution and think you can jump in and start working.

You have to work with the very few tools that are given to you. It could probably increase its flexibility and there could be more components added, which would make it more versatile. They could improve the solution by adding more components and by making it more feature-rich and including typical features that other more popular tools have.

There needs to be better support from the SAP support team. There needs to be more support for other programming languages like high-level C++, Java, or Python. That could be another improvement. 

HANA needs more integration with open-source tools, and with general reporting and analytics tools that are out there on the market. Once again, more integration on so many levels would be amazing. It's very SAP-centric and very proprietary right now. There are ways to connect SAP HANA with many tools already, however, in particular with open-source tools, if there could be even more integration, that would be helpful.

There needs to be more data transformation and more ELT features that can be implemented in the view. 

While I'm not exactly sure how long the company itself has used the solution, I've been dealing with it for four years at this point. It's been a while.

In terms of stability, I can't comment much. It depends on the underlying system and infrastructure, and it has the same kind of stability as any other on-premise solution. It doesn't have any cloud features such as multiple replication and multiple locations, et cetera. In that sense, it has the same stability as any other on-premise solution and does not guarantee any SLA. 

In terms of scalability, it's quite scalable. We've used it for production solutions very often and from any number of users. Generally, there are a few hundred users or so. I have not really worked on an implementation that uses thousands of users or anything that big, so I can't really comment on massive scaling. However, if it's for enterprise applications that have a few hundred internal users, it's good. 

The community support needs to be better. I haven't been impressed with it. In general, it just needs better support.

I have only worked on SAP and I haven't worked on other solutions.

I don't have information on the pricing, as that is an SAP and corporate-level agreement, which is not really known by all the in-house teams. I'm not really aware of the pricing. On the internet, I couldn't find much information about the cost of SAP HANA. I have heard that it is an expensive option. Being an enterprise-level solution, however, I don't have exact numbers. 

I'm not really part of the decision making team or the architecture team. I do not know if my organization has a business relationship with SAP or not.

I'd rate the solution five out of ten.

In the case of enterprise projects, I've heard that SAP HANA is used very widely. I would say, in general, it would be good to explore other alternatives, and not just go with HANA. It would be good to explore big data alternatives that are out there. They might be a better fit. Databricks these days seems to be quite popular. It might be an interesting alternative for some organizations. Depending on the use case, I'd recommend that other alternatives should be considered. If it's a reporting solution that people are building, which is using a lot of SAP internal data, then SAP HANA is a good option. Otherwise, other alternatives are out there.

The client is using the solution for supply chain management, and at the same time, our enterprise uses it to track the businesses' performance. The rest of our regions are going to be using SAP ECC. We are the first region to go with HANA. We were shortlisted to show them the roadmap and guide them. Supply chain management and tracking raw materials were areas of concern.

The IBP module was the most useful followed by the FI/CO and CNMM modules.

The product could be improved in several ways.

First, before carrying out a project with this environment size, a POC needs to be carried out, for which you would have access to various environments. And those environments are something that SAP should invest in and others should provide. That would be an improvement.

Second, some good amount of handholding, guidance, or other validation or certification from SAP at different levels.  

Third, access to tools for a longer period than the pre-defined trial version license. That's something that we can ask our friends from SAP to extend or make available in a different licensing model at zero cost.

I have three years of experience with the solution.

The solution is very stable. We would rate its stability as eight out of 10.

We would rate the scalability of the solution as eight-plus on a scale of one to 10.

The initial setup was pretty complex, considering the enormous amount of data they had from an Oracle ERP. Migration was an especially painful task, but we managed to sail through it thanks to the support of our customer. We delivered it within the timelines. We managed a few escalations. We worked with the customer. We had a weekly stand-up with the customer and various workshops and sessions to educate them and highlight the challenges. 

Implementation was completely in-house with a team of around 18 to 22 people and a couple of people from SAP, who looked at the overall program management level, providing guidance plus certifying that best practices were being followed and implemented. 

The deployment, moving from Oracle to SAP HANA, took around eight months

The customer took care of all the SAP license costs. Our scope was primarily implementation and migration support.

Oracle ERP had the flexibility, but it didn't have the functionality that the customer was looking for.

We would give the product an overall rating of nine out of 10.

We have an entirely SAP family, which makes it easy to manage and support. The customer opened its first, and we are doing multiple instances of SAP ECC implementations for the rest of the small countries in APAC, the Middle East, and Africa.

Around 175 to 250 people use the solution at every level of the customer's organization.

We will be providing maintenance for the next five years.

My advice would be to explore and play with the different systems available in the market. But, ultimately, look for a system with a brand, broad user usability, and support. For instance, my customer wanted to explore an open-source ERP. We persuaded him to go with SAP, primarily because they have the expertise. They adhere to the best policies. They offer support, etc. 

If you don't have all this, don't explore freebies. Go for a licensed version, recommended globally, and highly rated by Gartner or various research and consulting firms.

I have customers who work with SAP, and I carried out performance research for them, comparing the different parameters of SAP HANA. The solution is generally used for data warehousing. 

I think the in-memory database is excellent as it boosts performance. 

The product lacks some flexibility in its settings and configurations.

The solution is stable. 

The product is quite scalable.

I don't think the initial setup is too complex. Obviously it's not easy because SAP HANA is a complex system, so it's somewhere in the middle.

Licensing costs are quite expensive for the Ukraine but there is a range of different purchasing models so it's flexible in that sense. For a small enterprise, the costs might seem unreasonably high.

I rate this solution eight out of 10. 

The user interface is very good. You can do any kind of reporting analytics from the platform.

The solution needs to improve its integration capabilities.

There could be some debugging techniques when the solution goes wrong or if some of the data is wrong.

The solution needs to work a little bit faster.

When you do a report on a non-SAP platform, you face some compatibility problems.

I've been using the solution for seven years.

HANA is currently a stable solution after many upgrades. It's been seven years in the market, so it's fairly mature. It's been working fine for many clients here.

Scalability is good. That's the reason many customers like it. Initially, it was not so good and there were some problems with the software when it came to the market. Now it's fool proof in terms of running solutions for many clients. We typically handle enterprise-level businesses, so companies that have 500+ employees.

In terms of technical support, it depends on what partnership you have with SAP. If you're a platinum partner or a gold partner, for example, you can expect a certain level of support. 

The initial setup is straightforward. It's not too difficult to install if you are experienced with the solution.

We use the on-premises deployment model.

I'd recommend the solution. It's a very good product to learn and it's easy to use once you have an understanding of the technology. It's a nice product to work on.

I'd rate it eight out of ten.

Our primary use of SAP HANA is the use of modules, such as Material Management (MM), and Sales and Distribution (SD).

We have found the solution to be customizable and it is beneficial it comes as a bundled package. Additionally, it is user-friendly.

SAP HANA is not perfect and they could improve by having more options and more integration.

I have been using SAP HANA for approximately eight years.

The performance of SAP HANA is very good.

The solution is scalable.

We have a complete team size of approximately 12,000, including all the consulting and project managers.

We have approximately 36 end users, that directly impact the business. We might increase usage in the future but this depends on the business.

I have contacted the technical support from SAP HANA and they are providing a complete solution to customers. I have been satisfied.

The installation is straightforward and took approximately six months.

We used an in-house team to do the implementation.

We pay annually for the license of the solution.

I rate SAP HANA a ten out of ten.

We are solution providers. We are a supply chain organization and we deploy and supply chain solutions for our customers.

We have a host of solutions and for each of our customers based on their environments. We customize their platform and deploy it.

SAP HANA is one of our database endpoints.

It's easy to use, and the Hana Studio is pretty good.

The main issue that we are facing is with the connectors. The JDBC connectors are very slow. We have been trying to connect with our SAP HANA database to our customers.

It's a simple Java driver and there is no proper documentation available anywhere with clear steps. We have to rely on several documents which creates confusion.

The initial setup could be simplified.

Also, we don't have to option to pull up the data from the object structure in SAP HANA. We can only pull up certain objects. It doesn't provide you with a comprehensive list.

There are limitations in connection with SAP HANA. There has to be a better or easier way to connect the databases with other platforms, maybe using Java code or other types of code. It would be very good to have the documentation on how to connect.

I would like to have flexible connecting mechanisms for connection with Java or different types of solutions to SAP HANA on cloud or non-cloud solutions.

They could come up with something similar to the SAP HANA Studio type of modeling.

I would also like to see the capabilities to extend the API. If they had specific APIs, it would be easy for us to connect.

My company has been using SAP HANA for ten years.

We are using the latest version.

It's a stable solution.

It's a scalable solution. Because it's an on-premise infrastructure and SAP this is the best support for most of our customers, scalability is taken care of.

We are an SAP house. We have more than 1,000 people who use this solution.

I have not interacted with the technical support. Other teams may have, but my involvement is more with the integration. 

The initial setup was a bit complex. We were told to download it from the marketplace, but when we tried, it didn't work. We may have been doing something wrong, but we did not have a clear understanding of how it should be done. We also had difficulties with the trial version, it was not working.

There are two options:

1. Download SAP HANA then import it
2. Go to the marketplace and download the connector

For testing purposes, if they could provide us with clear documentation, it would be very helpful.

Licensing is on a yearly basis.

We are using the paid version. We pay $200 on a monthly basis.

I am not an expert in HANA. I build the enterprise bus that integrates with SAP HANA as well as other systems. We have built our own integrated platforms.

The recommendation of this solution would depend on the use case and the requirements, and the price will be considered.

I would rate SAP HANA an eight out of ten.

We have an ongoing cloud installation but mostly, we implement on-premises.

We use this solution for SAP Business One. 

It's used mainly for analytic purposes, reporting, and the processing of large data.

What I like most are the dashboards and pervasive analytics. Those are the most useful to us.

The documentation can be improved in the future.

In the next release, I would like to see integration with smart devices.

I have been implementing SAP Hana for six years.

We are using the latest version.

It's a stable solution.

SAP HANA is scalable.

We are project-based. In each project, there are anywhere from 30 to 50 users.

We have not really received any technical support from SAP HANA.

I think that's also one thing that maybe SAP would be most helpful, especially if we encounter several errors during installation. We don't get to have many references or we don't get to ask the technical guys of SAP HANA.

Previously we were using MySQL, but due to the fast performance of SAP HANA, we switched approximately three years ago.

In the newer versions, the initial setup is mostly straightforward. However, the older version was more complex. We had several issues with installing.

The installation usually takes approximately four hours.

There are two admins at the most to maintain this solution.

We definitely plan to keep implementing this product in the future and I can recommend it.

I would rate this solution a seven out of ten.