SAP HANA Reviews

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.

In our company, we utilized SAP HANA to manage various types of information, for example, inventory, employee information, and accounting-related tasks, such as billing and employee surveys. The majority of our employee information was stored in SAP HAHA.

As I only worked part-time on SAP HANA, I did not have the opportunity to explore the advanced features of the solution. However, I did work with basic features, such as user administration and access controls for the accounting department. The feature that stood out to me the most was the Single Sign-On and user administration, backup, and server management. My experience with SAP HANA was mainly focused on basic server improvements.

In my limited experience using SAP, the process of granting access to different modules is difficult. Specifically, the requirement to assign roles and key codes to users rather than being able to assign them individually made the process more complex. It would be beneficial if there was a way to assign key codes separately, rather than having to create multiple roles. This would make managing access easier.

The grid could be made more user-friendly. While it is functional, it is not as user-friendly as other databases or accounts. In particular, I find that SAP HANA is a bit more complex for users to navigate. This could be improved to better serve the user.

I have been using SAP HANA for approximately one year.

SAP HANA is a stable tool. On and off, there were some issues, but overall the experience was good and we didn't have any sort of trouble using the setup or any other users complaining about anything.

I rate the scalability of SAP HANA a ten out of ten.

We have approximately 70 users using SAP HANA in my company. We had some shared applications which were another approximately 30 users using the solution.

The solution is scalable.

I rate the scalability of SAP HANA a nine out of ten.

We provided support to our clients and we did not resolve ourselves we did not go to the vendor for an answer we looked online at the community support for our needs.

I rate the support of SAP HANA a seven out of ten.

Neutral

When comparing SAP HANA to other solutions in the same category, such as MySQL and Denodo, there are several differences. MySQL is more user-friendly than SAP HANA. Additionally, MySQL does not require a license to use, whereas SAP HANA does. However, SAP HANA does have its own advantages, such as being faster than MySQL and it is better suited for applications that require higher processing power. Ultimately, it depends on the specific needs of one's business and what they are trying to accomplish with their database which is the better solution. I find MySQL to be easier to work with than SAP HANA.

There is an annual payment needed to use the solution.

I rate SAP HANA a seven out of ten.

We use HANA mostly for any live reporting directly from the ECC box or S/4HANA box. We also do some of the operational reports, where it is difficult to do or apply the logic directly in the ECC box. It's better to bring the data, do your logic in SAP HANA and do your reporting out of it. Or you can also push your data to BW as well, by doing all your logic, and you can also expose your HANA calculation directly to SAP Analytics Cloud as well as Power BI.

The maintenance is quick. It's analytics directly out of the box. You do not need storage. You bring the data, do your calculation, and do your reporting. That said, if you want to store it, there's a cost involved. However, if you just want to report out of it, you don't have to move your data to any other place. I won't call it a data warehouse; it's more about quick analytic reporting out of SAP.

The speed at which it gets the data is great. There's a quick response time and quick reporting.

Most of what we need is already there. 

The initial setup isn't too difficult. 

It's a scalable product. 

It's still improving there, still improving a lot. Most of the extractors that are now. Most of the standard things don't satisfy the requirements in order to go for the custom build. More standards would help in the future.

I've been using the solution for five years. 

There are always stability issues. However, that is why we have SAP. I'd rate the stability eight out of ten. It's reliable. 

The solution can scale. I'd rate it nine out of ten in terms of the ability to expand. Of course, it comes down to cot. While it can scale, it will cost to do so. We have six users dealing with the product right now. Everyone in the organization is on HANA, whether it S4 or BW.

While I haven't dealt with support in the past year, they are usually pretty good.

Positive

You do need resources specifically dedicated to the solution. However, it's not that complex. I'd rate the ease of setup around six to seven out of ten.

It is pretty quick to deploy. Deployments happen weekly or biweekly. 

One resource is enough to handle deployment, and three for maintenance.

We have witnessed a very good ROI since you don't have to install a separate box. 

The main concern of every customer is the cost of the product. However, the pro is maintenance. You do not have to do a lot of maintenance on it. The number of results that you need after go-live would be less compared to any other data warehousing tool. You don't need a bunch of data engineers or data scientists, you just need a couple of business resources and a couple of analysts. In that sense, it costs less.

We're working with the latest version of the solution. 

I really like SAP. It's the best ERP tool. If you want to implement analytics, go with HANA. Go with SAP Data Warehousing if you want to implement a data warehouse.

I'd rate the solution eight 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 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. 

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.

My clients are using a specific technique called an in-memory database that is used with SAP HANA.

The solution can be deployed on the cloud and on-premises.

The most valuable feature of SAP HANA is the modeling of the databases.

The solution could improve in the handling of backup data and the administration tools.

I have been using SAP HANA for approximately seven years.

The solution is stable.

SAP HANA is scalable.

I have received a good response from the support from SAP HANA. However, the speed of the response could be better.

The standard way to implement the solution does not take a lot of time. However, if you need to use specific deployment options, called distributions, in the replication. It takes a lot of time for the configuration. The maximum time of deployment will be three days.

The steps taken for the implementation of the solution are sizing the resources, cloud or on-premise, and determining what modules will be required. The most important is figuring out the prerequisites and then starting the deployment. We have to check to see if all the licenses are in place, do application appraisals, and review the whole system.

There is a yearly subscription to use SAP HANA. There is a fee for maintenance.

I have over 50 customers using this solution.

I rate SAP HANA an eight out of ten.