Our company uses the solution for our accounting system and our services department. 

We have 60 companies so we take each project step by step. Most of our companies have been using the solution for one or two years so they have already converted to implementation or training phases. 

We have 18,000 users across all of our companies. 

The use case revolves around the ERP system, covering standard modules that begin with procurement, extend through sales, encompass the entire spectrum of business processes, including commercial aspects, inventory management, and production, and conclude with sales and financial tracking.

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

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.

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.

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.

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 use the solution for modeling and data extraction.

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.

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

We use it in order-placing and in the IBD integration, integrated business planning for forecast, and demand planning. I'm working in the sales and operation department. I'm not working in finance or production. Maybe the other teams are using it differently, or they're using different modules, however, for us at sales and operation, we are using it to place orders, developer CAST, track reports, and ensure accuracy.

I am currently using the latest version. But before that, before I jumped into the version, I used the initial version of HANA, as well. This initial version of HANA was not that great, it had a lot of bugs. But the latest version is very good. It's excellent.

I'm afraid that HANA is not a relational database, it's a column-level database just like Sybase IQ. Sybase is also an activity product, an SAP product. SAP bought Sybase in May 2010. So normal Sybase is RDBMS. Sybase has one more variant called Sybase IQ. That is not RDBMS, that is a column-level database. Normal Sybase is a whole-level database. That's a column-level database. So SAP HANA is based on this column-level architecture.

One more thing. The success of HANA primarily depends on the RAM and the storage. HANA became a success because the cost of the solar devices has fallen down substantially. I don't know about British Pounds, but in Indian Rupees, earlier in 2007, 2008, when I was working for Microsoft, one terabyte of a SAN device, used to cost around 22.5 LAK. I would say I would have had a 100,000. I think that's the nature. So one SAN device was costing 22 LAKs. The same SAN device, in 2013 and 2014, was costing around three LAKs. So the SAN device cost reduced by more than 200%.

Also, in parallel, the RAM cost also decreased, and the technology and the fastness of RAM increased. This impacted the primary condition for RDB and RDBMSs like Oracle, Sybase, SQL Server, and the like, that they need to support the foreign key relationship, where I have a few tables. For example, if I have five to six tables, suppose the first table is employment information. The second table is employee career details or his project, something like that.

Now, instead of populating the tables with the same information, the primary condition of RDBMS was to have a foreign key relationship between these two tables and reduce the redundancy. That was a primary condition, but in HANA, thanks to the cheap storage and high-speed RAM, I may not even bother to do a redundancy of data. I can combine all the tables and make a huge table. And as an entire table, whatever its size, I can pin the table in the RAM so that my access of information is not from the hard disk, but is directly from the memory, which is much, much, much faster. That is the beauty of HANA.

I primarily use the solution for data visualization and modeling. I've used the solution only from time to time for specific projects. 

This is an in-memory database. It's designed to leverage the use of new generation, multi-threaded CPU architecture. We are service providers.

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.

We use SAP HANA as the source of SAP or SAP S/4HANA. We don't have a BW system in between, so we assess data from SAP HANA DB, and we use HANA data models in the HANA database and consume those into SAP.

We are currently using the solution for planning, sourcing, and ordering from a contract perspective.

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.

We use SAP HANA for our BW system, which is the system we use for our BI tools and BI reports.

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.

SAP Business One works with SQL or HANA. My experience in HANA is configuring and administrating the database. We will also use it for the virtualization of all of our machines. 

We use SAP Business One and HANA as they have the same platform and databases.

There are no primary use cases of the solution in our company. We use SAP HANA as a database in our company because of the expiry deadline of our hardware, which is in January next year.

We use SAP HANA on a daily basis for end-to-end business processing. Also, we use it for maintenance management and appointing processes.

We use SAP HANA for Master Data Governance.

This solution is an advanced, analytical database, which supports in-memory computing.

I was using the product for some research in technical drawings - in terms of making some drawings, the different parts, and the structure of the machinery. I don't know if it's available in the SAP HANA, however, there is a model for this to schedule the maintenance. The company wasn't using it. Sometimes the product furnishes a lot of insights, cultural insights that the company still is not ready to implement.

We use it for database virtualization.

We use this solution to custom build features. We are customers of SAP HANA and I'm a solutions manager working for a retail company in Finland. 

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.

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 use SAP HANA for enterprise, financial, and materials management.

Our primary use case is for the database and the network.

We primarily use SAP HANA for machine learning and deep learning.

We are using on-premises, but I have also done some research in the last six months trying to go towards the cloud. We want to upgrade it because we also did the same thing with another company we are working with which is using the Sage X3 Cloud. We started with Sage Evolution, but now we are also moving to Save X3 Cloud.

I've recently left the company where we were using SAP HANA. Our use case was for replication so that end users could use dashboard reports. I'm a senior manager.

The solution is mainly for in-memory computing and past data processing, both columns or databases. It's a very good database.

I primarily use SAP HANA for procurement.

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 use this solution for our CRM, and for our ERP, inventory, and supply chain management. It's basically used to run the majority of the company. We are customers of SAP HANA and I'm an account executive. 

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

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.

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.

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.

We use the solution to store and migrate the data.

We are end users of SAP HANA and I'm assistant vice president of our company. 

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.

We're using the on-premises deployment model.

I am the technical consultant at our firm and our primary use case of the solution is to manage our databases. 

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.

We are using this solution for enterprise resource planning.

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

The deployment model used was on-premises.

We use this solution in conjunction with other prompted solutions primarily for real-time analytics.

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.

The internet of things, big data, and utilization of block chain will be possible with HANA.

We're writing SQL queries for the verification process, and we're using SAP master tables for tables. We write huge queries for processing data.

We primarily use the solution as a kind-of database for our workloads.

We have a lot of clients from different industries, such as factories and hospitals. We have deployed it on the cloud as well as on-premises for various clients.

We use a hybrid deployment model for this solution. Our primary use case of SAP HANA is for business intelligence. 

We are using this product for IAM.