A general introduction to HANA 2.0

with Multitenant Database Containers

(MDC)

Krisztián Pápai

April 4, 2019

Internal | SAP Employees and Partners OnlySMB Innovation Summit 2019

2Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

A general introduction to HANA 2.0 with Multitenant Database Container included

What’s different for Business One to launch HANA 2.0 when compare with adopting newer

HANA 1.0 as now?

A little bit complex but more flexible with HANA 2.0 MDC

Objects

What is Multi-tenant?

Perspective from database

4Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Multiple Components One Database (MCOD)

• One SAP HANA DBMS, one database, several schemas, several

applications

• Key tradeoffs:

− DB recovery available for entire DB (not available per

schema)

5Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Multiple Components One System (MCOS)

• More than one SAP HANA DBMS (with one DB in each), 1-n

applications, 1-n schemas

• Key tradeoffs:

− Contention for resources may negatively impact performance

− Additive sizing approach required

6Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Major partner vendors such as VMware and Hitachi offering HANA

deployments on their native virtualization technologies.

• TCO reductions and positive impact on capital expenditures

• Benefits of virtualization management layer for planning and

managing systems landscapes.

• Ease of HW replacements/avoidance of re-certification of OS &

SAP installations

• Starting small and scale along on need basis

• Private and Public Cloud offerings

Multiple Components / Instances, one System (MCOS,

Virtualization)

7Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP Multi-Tenancy OptionsHorizontal View

SAP HANA Instance

App X App Y

HW

OS

Multiple Components,

one Database (MCOD)

See Notes 1661202 + 1826100

Database

SAP HANA InstanceSAP HANA Instance

DatabaseDatabase

Schema X

App X

Schema Y

App Y

Hypervisor (just for Virtualization)

HW

OS OS

Multiple Components / Instances,

one System (MCOS, Virtualization)

See SAP Note 1788665

SAP HANA Instance

Tenant DBTenant DB

Schema X

App X

Schema Y

App Y

HW

OS

Multitenant Database Containers,

one HANA Instance (MDC)

See SAP Note 2096000

Schema X Schema Y

8Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA hardware deployment optionThird-party HANA virtualization and native HANA multitenancy

Virtualization and multitenancy are complementary offerings. Not competitive technologies.

SAP HANA Virtualization

Third-party virtualization/partitioning

technologies are leveraged to host multiple

isolated SAP HANA instances

SAP HANA Multitenancy

Every database tenant represents a dedicated

share of an SAP HANA instance data,

configuration, user management, and properties

SAP HANA Instance

HW

OS

Schema X

Database

SAP HANA Instance

App X

Schema Y

App Y

Database

SAP HANA Instance

Hypervisor

HW

OS OS

Schema X

Tenant DB

App X

Schema Y

Tenant DB

App Y

9Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Multitenant Database Containers vs Virtualization

Multitenant Database Containers(Native )• Lower TCO, single software stack

• Central configuration & administration (database level)

• Direct database resource management

• Optimized federation (performance benefits)

• Performance advantages (no virtualization overhead)

• Licensed via SAP HANA

Virtualization• Strong isolation

• Separate SAP HANA revisions option

• Standard federation (SDA)

• Additional virtualization license (e.g. VMWARE)

Positioning SAP HANA multitenant database containers

10Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Multitenant Database Containers provide strong isolation capabilities

• Each database containers has its own database admin and end users, database

catalog, repository, persistence, backups, traces and logs

• Database container Memory and CPU consumption can be configured independently

• Integration with SAP HANA data center operation procedures, housekeeping, backups

(full and/or on database container level), etc.

Multitenant Database Containers share one SID and Revision

• Shared installation of database system software

• Databases container are identified by name or port

• SAP HANA system replication covers whole system (system DB and database

container)

• Additive sizing for all database container

SAP HANA Multitenant Database ContainersSummary

Application

SAP HANA System

DB

container

Application

DB

container

System DB

11Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

New administration layer containing a System database

• Landscape topology information

• System-wide parameter settings

• Focal point for complete backup of all databases

• Resource management for all tenant DBs (CPU, memory, etc)

0 to n tenant databases

Individual backup/restore of tenant database

One database software version for a SAP HANA system (all

tenant databases and system database)

HA/DR setting covers whole SAP HANA system: all tenants

are included in a HA/DR scenario

SAP HANA Multitenant Database Containers

App

Connect to:

NDB.DB_A

SAP HANA

SID: NDB

NDB.DB_A

App

Connect to:

NDB.<port>

NDB.DB_B

NDB.SystemDB

B1 1.0 on HANA 2.0 MDC

13Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Key info: Full MDC support

Connect string (ODBC/JDBC) request

addition parameter for MDC

Using name of DB container

(Recommend)

Using SQL port (compatible)

Extracted/embedded SLD data

support (Option)

Install/ upgrade wizard enhancement

HANA High available support

HANA 2.0 with Multitenant Database Containers (MDC)HANA 1.0 with single

container mode

Wave 1: adopt HANA 2.0 with full MDC support

SAP HANA

Instance

HW

OS

Database

Company1

Company2

SLD

SBOCOMMON

COMM

Company x

SU

SAP HANA Instance

SU

HW

OS

DB A

Production

SU A

10.0 PL x

Company1

Company2

SBOCOMMON

COMM

SU

System DB

Company x

DB B

QA/ Test

SU B

10.0 PL y

Company1

Company2

SBOCOMMON

COMM

Company y

SLD (Option)

SLD

License

Monitor

&

backup

service

14Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

For Single-Database:

DRIVER=HDBODBC;UID=myUser;PWD=myPassword;SERVERNODE=myServer:30015;DATABASE=SLDDATA

For Multi-Database: (new DATABASENAME parameter)

DRIVER=HDBODBC;UID=myUser;PWD=myPassword;SERVERNODE=myServer:30013;DATABASENAME=DBA;

DATABASE=SLDDATA

ODBC connection string

15Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

New Installation & Upgrade to HANA2.0

Upgrade:

Ports and URLs will be not changed after the upgrade.

New Installation:

Tenant DB Port:

3<instance number>15

3<instance number>40 ~3<instance number> 99

SystemDB with port:

3<instance number>13

1st Tenant SQL Port

30015

SystemDB SQL Port

30013

SQL Port30015

Upgrade from HANA1.0 to HANA 2.0

16Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

The feature "SAP HANA multitenant database containers" (or, "MDC") was first introduced starting

with SPS09.

For B1H, will support MDC from HANA 2.0. Do not allow install/ convert to MDC in HANA 1.0

Architecturally, each database container has its own index server, and upon initial deployment,

consumes approximately 8 GB (before any application data is added). This means that the actual

number of databases container that can be deployed is limited by available resources; in other

words, a large number of very small databases container is not possible given the current MDC

architecture.

More information

Demo..

Multiple_containers: the only operational mode

HANA studio - add system: Single container

HANA studio - add system: Multiple containers

22Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

--Create

CREATE DATABASE mdc03 SYSTEM USER password "Initial0";

--Stop & start

ALTER SYSTEM [stop|start] DATABASE mdc02;

--Rename

RENAME DATABASE mdc02 TO mdc05;

--Check database container & its status

SELECT * FROM "SYS_DATABASES"."M_SERVICES";

-- Advanced feature

-- Create the fallback snapshot

ALTER DATABASE DEV CREATE FALLBACK SNAPSHOT;

-- Recover to point of snapshot

ALTER SYSTEM STOP DATABASE DEV;

ALTER SYSTEM START DATABASE DEV FROM FALLBACK SNAPSHOT

Sample: configuration from SystemDB

23Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Supported OS:

HANA 1.0 & HANA 2.0 can coexist in one OS

HANA 1.0 - 122.21

• SLES 11 SP4 ~ SLES 12 SP3

HANA 2.0

• Suggestion: SLES 15

Quick answer:

24Confidential: Released for Partners© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Call to action

• Explorer what’s new of HANA 2.0 from SAP Partner Portal.

• Top assets for sales and information to learn more.

• SAP HANA Academy – SAP HANA 2.0 Playlist

• Join Meet-the-Expert session for HANA 2.0 topic.

• Plan Early Bird Adoption with us

Thank you.

Contact information:

Krisztián Pápai

Solution Specialist

Krisztian.papai@sap.com

Gamification Challenge Code

NIC6a7cBy entering this SAP Breakout Session

code you will be granted 15 points

5

15