Expand +



SAP HANA One Illuminates New Possibilities

by Swapan Saha, Greg Chase, and Sapan Panigrahi | SAPinsider

April 1, 2013

SAP HANA One provides an instant deployment option that facilitates smaller SAP HANA projects and applications that are not easily accommodated by on-premise system procurement cycles. This cloud instance also means that users can turn SAP HANA on and off easily, allowing them to take advantage of it in their projects and to shut it off to save money when they no longer need it. In this piece, you'll learn more about SAP HANA One and its use cases.

Consider for a moment what it would be like if you could use SAP HANA like you would a light bulb, turning it on when you need it, and turning it off to cut costs when you don’t. Well, such a scenario is possible.

Of course, we’re not talking about the SAP HANA platform in general — we think of that as less of a common 60-watt light bulb and more the type of lighting that can power an entire city block. Rather, we’re referring to SAP HANA One, a smaller SAP HANA cloud instance. This cloud instance does indeed allow users to turn SAP HANA on and off easily and, while it might not be able to light up a city, it can certainly light up your smaller projects.

Gain Immediate Access to SAP HANA

SAP HANA One, currently available via Amazon Web Services (AWS), provides a single node 60.5 GB RAM instance of SAP HANA hosted in the cloud. SAP released this cloud version of SAP HANA to provide an instant deployment option that would facilitate smaller SAP HANA projects and applications that are not easily accommodated by on-premise system procurement cycles.

SAP HANA One is also perfect for what you might call “ask forgiveness, not permission” personal innovation projects. You don’t need to turn to the holder of your company’s SAP account for permission or to access the SAP Service Marketplace. You don’t need to call the sales department at SAP, wait for hardware delivery, or conduct systems installations. In short, you gain instant access to a fully enabled SAP HANA system by simply subscribing to it via the AWS marketplace. When you need SAP HANA One, you can turn it on. When you aren’t using SAP HANA One, you can turn it off and reduce your costs.

SAP HANA One runs on the AWS CC2.8XL system, which allows for 30 GB to 32 GB of compressed data. It can be accessed on demand by the system hour, or as a reserved instance at a monthly charge and discounted hourly usage fee. An instance can be spun up in as little as 10 minutes. As depicted in Figure 1, SAP HANA One gives users full access to SAP HANA functionality, just as if they were working with the SAP HANA platform. In addition, SAP HANA One provides an easy, web-based management console to configure and manage the instance.

 SAP HANA One gives users access to SAP HANA functionality in the cloud.

Figure 1 — SAP HANA One gives users access to SAP HANA functionality in the cloud.

A Comparison Between SAP HANA and SAP HANA One

SAP HANA One runs the same SAP HANA software available on the SAP HANA platform. The SAP HANA One base image is updated every four to six weeks with the latest version of SAP HANA software and additional web-based management tools and bundled components, which enable the deployment of SAP HANA applications in the cloud.

There are some key differences between the on-premise SAP HANA  and SAP HANA One, of course, other than the size of the instance. For example, SAP HANA One includes some unique bundled software and prebuilt templates, such as:

  • SAP HANA Cloud Integration, an extract, transform, and load (ETL) tool that ensures remote system data can seamlessly be moved into SAP HANA One.
  • The SAP Visual Intelligence templates, which, once connected, can be used to quickly visualize any business data brought over to SAP HANA One. The SAP HANA One community ( provides what we call “buy-or-try” links to download SAP Visual Intelligence, along with examples and how-to guides to use SAP HANA One out of the box alongside SAP Visual Intelligence.

Since SAP HANA One is deployed in the cloud, it also includes a couple of key benefits that an on-premise SAP HANA instance does not, such as:

  • On-demand availability: New instances of SAP HANA One can be instantiated and configured in minutes from various global locations.
  • Metered usage: Compute hours, transmission, and storage are tracked and can be stopped at any time to gain significant savings.

Other differences between on-premise SAP HANA systems and cloud-based SAP HANA One are summarized in Figure 2.1


Deployment Model 


SAP HANA on premise  





RAM for in-memory data storage


128 GB – 8 TB


30 GB – 32 GB


CPUs (cores)


2 CPUs/20 cores – 128 CPUs/
1280 cores


2 CPUs/16 cores


Hardware location


In customers’ data center


In Amazon Web Services (AWS) region




Upfront perpetual software licenses, hardware, power, and IT personnel



US$3.99 per hour of system usage on demand*

US$2.49 per system hour of reserved system usage*



High-availability capable


Not high-availability capable


Time to provision


Weeks to months




Licensing agent






*Hourly cost estimate includes compute, storage, and data transfer

Figure 2 — A comparison between SAP HANA, deployed on premise, and the cloud-based SAP HANA One.

Usage Scenarios for SAP HANA One

SAP HANA One allows customers to access an SAP HANA system in an on-demand, elastic fashion without having to wait for hardware delivery or system setup. This is extremely helpful for light-bulb-sized productive scenarios,2 such as:

  • Small projects: SAP HANA One is perfect for small projects, regardless of the size of your data, the amount of complex or unrelated schemas, and the potential need for ad hoc queries. Such projects might include using SAP HANA One with a product pilot or a smaller or occasionally used third-party application, or cases when a cloud deployment option makes more sense than initiating a hardware procurement cycle.
  • Starter projects: SAP HANA One can be used in the early stages of an implementation or during the development of applications and data models that may eventually be deployed in an on-premise SAP HANA system. This approach of trying out SAP HANA One first and then moving to an on-premise SAP HANA system can accelerate implementations of applications, which can be instantly cloned from preconfigured template systems in the cloud.
  • Temporary projects: These include projects with a limited lifetime, such as data collection and analysis for events and marketing initiatives, or data sharing with business partners. These kinds of projects could also include demos and evaluation instances for applications.

In short, even in situations when productive use of an application will require the larger capabilities of an on-premise system, SAP HANA One helps users speed up sales cycles by quickly getting their applications and solutions into the customers’ hands for evaluation and setup. And, if an application deals with smaller datasets or requires primary access via mobile devices, or if the customer prefers to keep its application data separate, using SAP HANA One instead of an on-premise SAP HANA instance is often the ideal solution.3

The Future of SAP HANA in the Cloud

SAP HANA One continues to evolve at a rapid pace, updating at least quarterly to include functionality from new versions of SAP HANA software and datasets. Planned future updates will include SAP HANA support package stack 6, as well as templates and adapters for scenarios that may include:

  • MySQL application data connectors
  • Elastic turbo-charging of specific SAP ERP business processes
  • Public sector-specific applications, such as healthcare fraud detection and education
  • Powerful bundled server-side business intelligence tools

For more information about SAP HANA One, see the “Frequently Asked Questions” section at

To find out how SAP HANA One can help you get started with a productive SAP HANA system in the cloud in just minutes, visit, hover over the “Learn” dropdown menu, and select “SAP HANA in the Cloud.”


Swapan Saha ( received his Ph.D. in Electrical Engineering from Iowa State University in 1996. In 2011, he joined SAP where his focus has been on architecture and performance engineering. Since 2011, he has been involved with SAP HANA and is currently a Senior Director focusing on bringing SAP HANA to the public cloud.


Greg Chase (; Twitter: @GregChase) is an enterprise software marketing executive with nearly 20 years of experience in marketing, sales, and engineering with software companies. Most recently, Greg has been passionately advocating for innovation and transformation of business and IT practices through cloud computing and business process management in his role as Senior Director of Marketing at SAP.


Sapan Panigrahi ( is Vice President of SAP HANA Public Cloud Engineering at SAP. Sapan joined SAP in 2011 and started working on SAP HANA Cloud. His current responsibility is to promote mass adoption of SAP HANA in the public cloud. Sapan has deep expertise in large-scale infrastructure, distributed systems, search engine technology, and performance optimization.


1 For more details about supported SAP HANA on-premise hardware, see the SAP HANA Product Availability Matrix available at the SAP Service Marketplace (S-User required): [back]

2 For additional information about usage scenarios for SAP HANA One, visit [back]

3 To learn more, see [back

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!