Illustrating Deployment Options

Objectives

After completing this lesson, you will be able to:

  • Identify deployment options for SAP HANA

SAP HANA Deployment Options

Business Example

At the time of its market introduction, SAP offered SAP HANA following an appliance model – a certified combination of hardware and software that could be deployed as an on-premise solution. Meanwhile, SAP is continuously working on increasing the flexibility and choice of deployment options for SAP HANA. For customers, it is essential to understand which deployment options exist, what their capabilities and limitations are, and which scenarios can be combined and run together on one SAP HANA server or database.

SAP HANA can be deployed in on-premises, in the cloud, or even as a hybrid deployment where on-premises and cloud are combined. Which option is chosen depends on the customer's requirements. A new customer might start with a 100% cloud strategy in mind, whereas a longtime SAP customer over time wants to move to cloud solutions.

With SAP HANA deployment options, you can distinguish between a preconfigured on-premise appliance, SAP HANA tailored data center integration (TDI) deployments, an SAP HANA Cloud deployment, or a hybrid deployment model that combines cloud and on-premise instances.

Technical Deployment Options

The technical deployment options determine how SAP HANA systems, the hosts used for SAP HANA systems, and applications running on SAP HANA are deployed.

To run multiple scenarios on one system or database, you need to understand the availability and capabilities of the technical deployment options.

Technical Deployment Options

  • Multi-tenant Database Container (MDC)

  • Single Application on One SAP HANA System (SCOS)

  • Multiple Components on one Database (MCOD)

  • Multiple Components on one System (MCOS)

  • SAP HANA with Virtualization

Multi-Tenant Database Containers

SAP HANA multi-tenant database containers establish a foundation for providing multi-tenancy in SAP HANA.

As of SAP HANA 2.0 SPS01, an SAP HANA system is installed in multiple-container mode. It can contain more than one multi-tenant database container.

A multiple-container system always has exactly one system database, which is used for central system administration. It also has any number of multi-tenant database containers (including zero), called tenant databases. An SAP HANA system installed in multiple-container mode is identified by a single system ID (SID). Databases are identified by a SID and a database name. From the administration perspective, there is a distinction between tasks performed at system level and those performed at database level. Database clients, such as the SAP HANA cockpit, connect to specific databases.

All the databases in a multiple-container system share the same installation of database system software, the same computing resources, and the same system administration. However, each database is self-contained and fully isolated with its own, as follows:

  • Set of database users

  • Database catalog

  • Repository

  • Persistence

  • Backups

  • Traces and logs

Although database objects such as schemas, tables, views, procedures, and so on, are local to the database, cross-database SELECT queries are possible. This supports cross-application reporting, for example.

SAP HANA multi-tenant database containers allow you to manage several databases in one database management system. Note that a single database container is also called a tenant database.

Concept and Terminology

The concept and terminology of SAP HANA multi-tenant database containers are as follows:

Concept and Terminology of SAP HANA Multi-Tenant Database Containers

  • Run multiple tenant databases on one SAP HANA system

  • Run and support multiple applications or scenarios on one SAP HANA system in production

  • Strong separation of data and users

  • Backup and restore available by tenant database

  • Resource management by tenant (CPU, Memory)

  • Move or copy tenant databases or applications to different hosts or systems

  • Integration with existing data center operations procedures

Single Application on One SAP HANA System

A single application on one SAP HANA system is also known as Single Component on One System (SCOS).

To more readily describe the various other options for technical deployment, it is useful to first illustrate the simple, straightforward approach to deploy an application on an SAP HANA system. This will be useful for comparison purposes.

In this configuration, a single application runs in a single schema, in a single SAP HANA database as part of an SAP HANA system. This is a simple, straightforward scenario that is supported for all use cases without restriction.

Multiple Components on One Database

Multiple applications on one SAP HANA system are also known as Multiple Components on One Database (MCOD).

The technical deployment type MCOD refers to the scenario where more than one application, scenario, or component runs on one SAP HANA system. This deployment type is available with restrictions for production SAP HANA systems. For production systems, there are allow lists that specify supported scenarios explicitly.

Multiple Components on One System

Multiple SAP HANA systems on one host are also known as Multiple Components on One System (MCOS).

SAP does support running multiple SAP HANA systems (SIDs) on a single production SAP HANA host. This is restricted to single-host or scale-up scenarios only. Multiple components on one system requires significant attention to various detailed tasks related to system administration and performance management.

Production support is restricted to SAP HANA SPS 09 or higher because of the availability of some resource management parameters (for example, affinity). Running multi-SID on one SAP HANA host can impact the performance of various types of operations, because competition for computing resources might occur (memory, CPU, I/O, and so on).

Perform the requisite testing in every project before going live. In general, stress or volume testing provides good indicators of the expected performance. When operating a system that features a multi-SID deployment, use the resource management features of SAP HANA (for example, parameters controlling memory limits, and influencing utilization of CPU cores, and so on) to optimize performance.

Virtualization

SAP HANA supports many popular virtualization supervisors, such as VMware vSphere 5.1 or newer, Hitachi LPAR, Huawei FusionSphere, IBM PowerVM, or others for non-productive environments. You can choose virtualization for a wide variety of configurations, for single and multiple virtual machines, in single- or multi-node configurations, for appliances of SAP HANA and SAP HANA tailored data center integration delivery methods.

The technical deployment type, SAP HANA with virtualization, refers to the scenario where one or more SAP HANA database SIDs are deployed on one or more virtual machines running on SAP HANA server hardware.

One benefit of virtualization is that you can assign dedicated CPU and memory resources to specific databases and increase the flexibility of hardware usage.

For customers already standardizing on virtualization technology, SAP HANA offers the customer total cost of ownership reductions and additional options for planning and managing their systems landscapes, as follows:

  • Ease of hardware replacement and avoidance of recertification of OS and SAP installations

  • Separation of IT ownership (hardware and software layer)

  • OS-independent monitoring

  • Low-cost High Availability (HA) capabilities in development and test environments

  • Positive impact on capital expenditures

Related Information

SAP HANA, Express Edition

SAP HANA, express edition is a streamlined version of SAP HANA that can run on laptops and other resource-constrained hosts, such as a cloud-hosted virtual machine. SAP HANA, express edition is free to use for in-memory databases up to 32 GB of RAM.

Memory capacity increases beyond 32 GB are available for purchase at the SAP Store.

SAP HANA, express edition is available for download from the SAP developer center free of charge: download page for the SAP HANA express edition. This version of SAP HANA can be installed on laptop or desktop computers, Linux-based servers, virtual machines, or a private cloud.

For more information on SAP HANA deployment options, see the following SAP Notes:

  • SAP Note 1666670: SAP BW powered by SAP HANA - Landscape Deployment Planning

  • SAP Note 1661202: Support for multiple applications on SAP HANA / tenant DB

  • SAP Note 1826100: Multiple applications SAP Business Suite powered by SAP HANA

  • SAP Note 1681092: Multiple SAP HANA systems (SIDs) on the same underlying server(s)

  • SAP Note 1788665: SAP HANA Support for virtualized / partitioned (multi-tenant) environments

Log in to track your progress & complete quizzes