SAP HANA Reviews

We use SAP HANA mostly for fetching data. There are a lot of tables for which we need to do some troubleshooting. For example, if the fill rates are low daily, we examine various factors, such as yield production versions and inventory levels, to understand why it is happening. To assist us in this process, we leverage Blue Yonder ESP, which operates on HANA View. As a supply chain consultant, we use SAP HANA to fetch data from these tables to troubleshoot the issue and find out why the fill rate is dropping. This helps us determine if it is a genuine issue related to supply or something related to the model.

We have been building a lot of sniffer audits for users. For instance, if a bond structure is not going a particular way, the master data team and the business users can check those audits. These audits, made to assess the data quality, will confirm if it is something we have already identified. So all the data quality audits are built on HANA View.

SAP HANA's interface is pretty user-friendly. It is not very difficult to pull out data extract, and even a beginner can fetch data easily. Additionally, data snapshots are available. Also, building upon a more advanced query is not that difficult. In terms of usability, SAP HANA is pretty good.

SAP HANA's long run time to extract data could be improved upon. Also, the analytics given in SAP HANA's interface is basic and could be improved upon.

I have been using SAP HANA for a year.

I rate SAP HANA an eight out of ten for stability.

I rate SAP HANA a seven out of ten for scalability. SAP HANA can be used in the tactical horizon, which for us is 52 weeks. Anything beyond that needs scenario-based planning, which is not possible with SAP HANA.

Around 5,000 to 6,000 users are using SAP HANA because we are a team spread across the globe in places like Boise, the US, Singapore, Japan, Taiwan, and India. The first users are supply chain engineers and IT employees. Business users hardly use it because it is a little complicated for them. Since we are trying to expand our tactical horizon from 12 months to 18 months, the usage of SAP HANA will increase in the future.

SAP HANA's technical support is pretty good.

Positive

Before using SAP HANA, we were entirely using SAP APO. We switched to SAP HANA because it is an optimizer and gives better results than SAP APO.

I rate SAP HANA a seven and a half out of ten for its initial setup. The deployment of SAP HANA took around 18 months.

The major part of the deployment was done internally. However, initially, we did use external consultants. So SAP HANA's deployment was partly internal.

The first step in the deployment process is customization, which involves obtaining the solution according to our requirements, including the data we use and the basic tables it provides. Our bond structure was changed to enterprise bonds so SAP HANA could process it. An IT team worked entirely on the data transformation part to ensure the data from other upstream systems could be processed. After that, we went into the design part, the user acceptance testing, and finally went live.

New users of SAP HANA need to have basic SQL coding skills and attention to detail to see data using the solution. It might be complicated for someone, not from a background where they're used to seeing a lot of data.

Overall, I rate SAP HANA an eight out of ten.

We are using the solution for the DW system. The primary function of the solution is for the database in memory.

I would like to see improvements in the connectivity of the solution with other BI software. Not every software can connect to it natively.

I have been using the solution for the past five to six years.

I would rate the stability of the solution an eight out of ten.

I would rate the scalability of the solution an eight out of ten. The solution is quite scalable. You can increase the usage if you have enough hardware. There are about 5000 users in our organization.

Previously, we used Oracle Database, but we have changed to HANA database now.

The initial setup was not easy since it took a couple of days to install the tool. We had to download it from the internet and follow some processes so that the tool could be integrated into our internal network.

The deployment of the solution was done in-house.

I would rate the pricing of the solution a ten out of ten. The pricing for on-prem SAP HANA is on a yearly basis and expensive. I am not aware of the actual pricing but it is based on 64 Gigabytes. For instance, if you consider $10,000 for 64 Gigabytes, then you can calculate the cost for Terabytes in case you have one. You will have to buy expensive hardware as well which is quite a lot.

I would rate the solution a nine out of ten. There are three SAP-based individuals involved in the maintenance of the solution. This solution is recommended for SAP-oriented users only since it is very expensive as a database.

We have used SAP HANA to do some tendering through the supplier management system. We have our own servers that are hosting the solution.

Primarily we use SAP HANA to manage suppliers, they can upload the tender documents. We are then able to do prequalification based on the preset requirements. We then know who is qualified and who is not. Additionally, it has helped us send notifications to the suppliers.

Using SAP HANA has reduced a lot of paperwork that we would typically be doing and the communication we have with our suppliers. Additionally, it has improved our organization and approval process.

The most valuable feature of SAP HANA is the interaction it provides with external suppliers and clients.

When we are using SAP HANA we have some difficulty with the customization. We would like to be able to add and make customized menus.

In a future release, there should be a way to cancel or delete, for example, a tender document. The deleting or canceling of documents is sometimes confusing.

I have been using SAP HANA for approximately three years.

SAP HANA is a stable solution. 

The scalability of SAP HANA is good.

We have more than 500 people using the solution plus the suppliers we have. We can give suppliers accounts. 

I have used the support from SAP HANA. We have expectations some of our problems should be fixed in 24 hours but they are not fixed for 48 hours. It's not that the support does not know how to do it, but sometimes it takes a little bit longer for them to have our solution.

Neutral

I have used previously Oracle and Microsoft Innovation. We switched to SAP HANA because the cost was more favorable than Oracle and it was more user-friendly.

The initial setup of SAP HANA was gradual, it took us approximately six months.

We used consultants, project managers, and our team to do the implementation of SAP HANA. The solution is stable and we do not have to do a lot of maintenance.

There is an annual license to use SAP HANA.

I rate the price of SAP HANA an eight out of ten.

My advice to others is for them to do a lot of research and training before they decided to go live with the solution.

I rate SAP HANA an eight out of ten.

We are consolidating SAP HANA into our environment as one of our primary projects. This is not a greenfield implementation, but rather a conversion from our current environment to the consolidated project, where multiple databases are combined into one. So far, this has been going well, and the major advantage of SAP HANA is that it can read both rows and columns at the same time, unlike other databases. Despite this progress, we still need to evaluate its performance as it has not been as fast as we initially anticipated.

This database for SAP is deployed on-premises, and it supports over 40 SAP applications in our environment.

I provide the infrastructure support for data centers and databases, and I can see that the background jobs run much faster with SAP HANA than with Oracle or DB2. Furthermore, SAP HANA has fewer licensing issues, making it cheaper than Oracle. Additionally, the support for SAP HANA is the best we have seen.

The best part of our multi-node system is its ability to help us a lot. This system consists of a primary and secondary node, which is a database, and it works effectively. 

SAP's HANA database is said to be the fastest database, with simultaneous reading and writing of rows and columns. However, we have not seen the promised improvement in speed. Additionally, shutting down a large database of 6 TB can take up to 30 minutes, whereas databases of other types are much faster to shut down. The long recycling process of HANA can be quite frustrating and has room for improvement.

When there is blocking occurring on the database level, the process responsible for it should be killed automatically. We have not seen any CPU or memory increases, but often the memory is almost completely utilized in Linux environments where HANA is installed. As HANA cannot be installed on any other OS, the memory usage should be checked to determine why it is almost entirely taken up.

The cost of the solution is high and has room for improvement.

I have been using the solution for almost five years.

I give the stability of SAP HANA an eight out of ten.

I give the scalability of SAP HANA a six out of ten.

The return on investment is good and that is why we are moving ahead with the transition.

SAP HANA is expensive, but unfortunately, we do not have any alternatives. Therefore, we must transition to HANA databases by 2025.

I give the solution a six out of ten.

Anyone currently using SAP will be transitioning to HANA. Those who wish to implement SAP will also be using HANA, as it is the only supported platform for SAP applications, not for any other applications.

We have a full landscape for SAP. Currently, my customer is using it. We are using the native HANA for the non-SAP sources.

We have our data nodes for different business domains. The data is coming from non-SAP sources. The data is coming from different systems. We have a database warehouse approach.

The solution is very fast in terms of memory. It's very convenient and very innovative. It's very good at handling the input and output of the data. There is no lag.

It has become the base of building graphical calculation views. 

It is very convenient when you are working with Postgres or Snowflake. When you have modeled everything correctly, it's easy to translate the model. 

With the way native works, it builds a good platform. It's not just a database. It's much more.

It has an inbuilt smart data integrator which you can use for sourcing, researching, and loading the data. It's included in the web IDE version of the web HANA deployment. 

This is a very mature product. The performance is very good. 

I cannot think of any features that are missing at this time. 

In the calculation views, the functions that have been provided to build the graphical views should be enhanced and could be made more flexible. There should be more functionality available.

You cannot apply mulit-join inside the calculation views, for example, when you are joining tables. You have to do it in a four-node. You have to join them one by one instead of joining everything together in one step. 

I've been using the solution for six years. 

The performance is good. It is mature and stable. I've never experienced any issues like crashing or freezing.

The scalability is very good. I'd rate it 8.5 out of ten in terms of ease of scaling. 

This is a good solution for enterprise solutions. 

In terms of the initial setup, I do not know how to install it on the server itself. I don't handle the technical aspects since I am a consultant. I don't directly handle the setup process. Likely, it is installed on Linux.

While my understanding is the product is likely expensive I do not handle the pricing. I don't know the exact costs. 

Smaller companies may not be suitable as the pricing is quite expensive. Even medium-level companies would have trouble affording a full SAP stack. An enterprise would have the budget to take this solution on.

The cloud may be more affordable, however, on-prem would be very expensive. 

I'm a consultant. 

In terms of relational databases, this is the best option.

If you are going to work with HANA, make sure to use the latest version. It has the latest approaches.

Users should utilize the HANA platform to the fullest extent. Get the most out of it by using all of the tools, as much as possible. Don't just use it as a data model database.

I'd rate the solution nine out of ten. 

They should develop and improve the solution's data management system. They should also work on the capabilities and features of their mobile and cloud applications.

We have been using the solution for five years.

The solution is highly stable once configured. It requires regular garbage collection activity to function smoothly. Also, it depends on the implementer and vendor's services.

I rate the solution's stability as an eight.

I work with an enterprise business client with 500 users using the solution. Based on the requirement, the solution allows us to scale up our capabilities and business processes.

Thus, it is scalable, and I rate the scalability as an eight.

The solution's initial setup is straightforward, but it requires experience for implementation.

On average, it takes six to eight months for deployment. There are some instances where it takes a year when the client wants to combine two solutions together.

We use SAP's new project management model for deployment. It is a complete infrastructure service where we get the hardware from hyperscaler and implement the application.

Our implementation team includes business, functional, and POD consultants.

The solution's licensing is expensive for SMEs and large enterprises alike. There are no additional costs included.

I recommend the solution to others and rate it as a nine. In comparison with other DMS solutions, it offers good performance and is excellent in administration management. It has a simple table structure that makes it a high-performance system for customers. I advise others to select an implementer with knowledge and experience in using the solution.

We primarily use SAP HANA for ERP in the manufacturing and delivery industries.

What I like best about SAP HANA is that it's faster than Microsoft SQL Server.

The SAP HANA interface has room for improvement because it takes more work to manage than the Microsoft SQL Server interface.

Nowadays, you'll see more no-code tools in the market with a drag-and-drop feature, and that's what I want to see in SAP HANA in the future.

I've been using SAP HANA for six months.

SAP HANA is a stable product. Its stability is eight out of ten.

The scalability of SAP HANA is a six out of ten.

My company used to work with Oracle Database version 10.2, but migrated to Microsoft SQL Server and now also using SAP HANA because Oracle Database is expensive, plus it requires users with a higher level of experience on Oracle Database.

The initial setup for SAP HANA is so-so. It's not easy, yet it's not so difficult. I'm rating its setup as six out of ten.

The total time it takes to deploy SAP HANA depends on the type of integration. I have a lot of integrations where one integration gets deployed within thirty minutes, while another takes more than two days to deploy.

The pricing for SAP HANA is high. It was expensive. You have to pay a lot, and it's the highest-priced solution in the local market, though when you compare it to other tools in the global market, the price is similar.

You pay a lot for the license, and you also have to pay for some add-ons.

I'd rate SAP HANA licensing fees as two out of ten.

My company uses SAP HANA.

My company has SAP Business One version 9.3 that integrates with SAP HANA, but I haven't worked much on SAP HANA yet.

I'm a user of SAP HANA, not a partner.

Around thirty people, mostly technicians, work on deploying SAP HANA. The solution requires five to six engineers for maintenance.

My company has eighty-eight SAP HANA licenses used mainly by the end-users, for example, managers.

I'd tell anyone looking into using SAP HANA that it's a good tool but expensive for smaller-scale companies.

On a scale of one to ten, I rate SAP HANA as ten because it's a good tool, and I like its technology.

SAP HANA is one of the best databases known for its performance. Since the solution offers a functionality known as in-memory computing, its performance cannot be measured with other databases. If a customer has a large amount of data, especially data in gigabytes or terabytes, because of which they face performance issues, then SAP HANA is the database for them.

SAP HANA should go for big data solutions as well. So, SAP HANA is good for large enterprises and large databases. Even for large databases, we have to rely on other tools, especially those that fall under big data solutions. Hence, SAP HANA needs to be a part of big data solutions.

SAP HANA has almost all the features, and with every new release, they are introducing some new features because of the development team working on the solution. The solution has started supporting its integration with other applications, which can ensure the solution's development. The solution's development platform should be more flexible and scalable to adapt to other solutions. In short, the development environment of the solution needs to improve. Such improvements will make the integration and adaptation of the solution more flexible.

For almost four to five years, I have been working on SAP HANA. I am not only an end user of the solution but also a part of a company that provides the solution to its customers.

The new version of the solution is stable. SAP HANA Version 1.0 had some performance issues, but after SAP HANA Version 2.0 got introduced, the solution became more stable. So there is no need to put in more effort since most things have become automated in the solution.

It's a scalable product. Scalability-wise, I rate the solution a nine out of ten. Presently, we have around 15 customers.

Since I haven't faced any issues with the solution, I haven't contacted technical support yet.

The solution's initial setup was straightforward.

Only one or two days were required for the deployment part, which the technical department took care of in our organization.

If SAP provides simple and standard documentation to its users explaining every solution process in detail, the steps to deploy the solution can be simplified. In short, the deployment process won't take long if one follows the documentation. Also, it will ensure that the users do not have to get involved in any troubleshooting steps or face any other problems while using the solution.

Only one system administrator is required to deploy and maintain the solution.

SAP offers a license for both ERP and HANA, which means that if you purchase SAP ERP, you will be provided with a license that covers both products. In the case of on-premises deployment, the license is perpetual, which means that you only need to pay for annual maintenance. On the other hand, for cloud deployment, licensing payments are made on a yearly subscription basis.

While the cost of the license may seem high, it is important to note that the benefits of the solution far outweighs the cost. Therefore, it can be considered a normal cost.

I would tell those planning to use the solution that it works fine but needs to become more portable. The solution should also be made capable of supporting non-SAP application environments. Overall, I rate the solution a ten out of ten.