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 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.
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:
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 use it for database virtualization.
The main feature is that the processes are very flexible, they are able to be adapted to the business and their departments. The solution is very good and has covered all functional areas needed in this type of solution.
There could be better management for faster updates, last year there were some changes in India to the e-invoicing feature. During that time, there was a couple of updates that we had to wait until the release happened before we could do the implementation, this was a time we had to wait. They are pretty good at releasing updates but that time it was not the fastest.
I have been using the solution for a few months.
I have found the solution to be stable, it is very robust.
There is the ability to scale the solution by increasing capacity with no problem, it is very flexible. We have almost 34,000 users using the solution.
We had some issue with support in the past because they did not have enough availability. However, they have improved and now they are okay.
Since we have been using the solution before we did not have any issues with the install. There were not any major complex operations. However, there were some challenges but we had the full documentation with us and it was not a problem.
The price of the solution could be reduced, it is expensive. If they wanted to go into other industries and sectors the cost is on the higher side. They cannot go into each and every sector. If the cost was more reasonable, then it would be easy for them to enter more markets. This would be a disruptor in the industry because it would be used more often than other solutions, which would be good for the company.
I do recommend this solution but at the same time, it is expensive. The cost will not be able to be afforded by everyone such as medium and small scale businesses.
I 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.
We use SAP HANA as our primary database for our enterprise business. The product is centrally hosted where all our business departments access the product through its sister product SAP ERP.
The product hosts data for the deployed modules namely, Finance and Control (FICO), Materials Management (MM), Plant Maintenance (PM), Production Planning (PP), Quality Management (QM), Human Capital Management (HCM), and Sales and Distribution (SD).
It also hosts the business warehouse (BW)/BI environment.
The performance in terms of processing time is unmatched due to the in-memory processing capability.
The administration of the many records that were previously distributed in different systems into a central location has been made easier. All that information has been availed central from multi-locations without the requirement for manipulation using worksheets, as was the case before.
The database is also running our business warehouse and business intelligence environment, where insightful reports are generated for business management.
Security and performance are the two most valuable features. Our processing time came down to less than two hours from more than ten hours in the legacy system. We use the product to process our small-scale grower payments at the end of the month and whose daily tea deliveries records are in hundreds of thousands.
The audit trails in the HANA product are so robust that one can trace back to the tiny details of what happened at a particular time, who did it, and the time it was done. This makes auditing of both the transactions and performance of the product possible.
The product is very demanding on memory requirements. This is a result of it being an in-memory processing product. The choice of the hardware must be done carefully because when subject to other hardware, it gets slow and just crawls. Memory on the other hand is not cheap because you have to buy it from a third-party.
The cost of the database is not cheap either, as you have to pay for the runtime for any licenses that you purchase, and that comes each year. Now that is punitive with increasing license requirement.
We have been using SAP HANA for six years.
This is a very stable product.
SAP HANA is very scalable.
The customer service is excellent, whereas the technical support is not among the best but we managed.
We used another solution before this one and we switched due to data growth and the need for predictive management.
The initial setup is complex.
SAP itself assisted us with deployment.
Setup and licensing require planning and proper budgeting, as it is not cheap.
We evaluated products by Microsoft and Oracle.
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.
We primarily use SAP HANA for machine learning and deep learning.
The solution is very stable.
The solution can scale well.
We've had good experiences with technical support.
The performance is excellent.
We use SAP HANA in our projects but it's very expensive for our projects. We need a relational database in-memory that can handle these issues.
The solution is very expensive for us.
It's hard for us to find test users and sometimes we need them to connect to SAP from Iran, however, this is an issue due to the sanctions against the country.
We've been using the solution for more than six years.
We've found the solution to be very, very stable, especially when you compare it to other solutions.
The solution can scale quite well. If a company needs to expand it so that it fits their growing needs, they can do so easily.
The technical support on offer is very good. We're quite satisfied with their level of service.
We tried GQ database but it's not a stable database. Sometimes the results weren't correct. SAP HANA is much more stable, which is why we use it, even though it's expensive.
The solution is very pricey. We're looking into other options because of this.
We're looking at Oracle products as an option right now. We're also looking at MAT-V, a CPU-based database it's very fast, however, we do occasionally face issues with it.
We are a customer. We don't have a professional relationship with SAP.
SAP HANA is not just a memory database, it's a big platform. It's a very, very safe database. It's a very safe database and the performance is very, very good for an in-memory database. For example, sometimes we use Oracle databases 18C or 19C. The data is in the memory, however, when data is running, it's very slow, due to the fact that all data is in the memory and you need to and go to write disk.
Sometimes when the data is very large, we might scale up our approach, and, in the scale-up approach, sometimes it is slow in HANA. That said, the scale-up approach is very, very good. SAP has got one problem. When you start the database, all data from the tool's memory takes a very long time. We've found that IBM's non-volatile memory is better than internal memory. New users just need to be aware of that.
I'd rate the solution nine out of ten. The solution, overall, has fantastic performance, however, the cost makes it really hard for us to keep using it.
The solution is mainly for in-memory computing and past data processing, both columns or databases. It's a very good database.
The solution offers very good in-memory computing.
We can save data very easily.
It is easy to set up. The implementation process is quite straightforward for us.
The solution is stable.
There are limitations on tables. There is a two billion record limitation on a table. We'd like it if there could be more. If a table passes two billion records, SAP goes down.
The pricing is expensive.
I've dealt with the solution since 2012. It's been about ten years or so. We've used it for around a decade now.
It's very stable. We've been using it for almost ten years and haven't had any issues. There are no bugs or glitches. It doesn't crash or freeze.
The solution is very straightforward and simple. It's not overly complex or difficult.
It's quite a costly product. It is expensive. I'd rate it four out of five in terms of the level of expense.
I'd rate the solution ten out of ten. It's one of the best databases in the world.