SAP HANA SPS10- Multitenant Database Containers

1© 2014 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA SPS 10 - What’s New?
Cloud, Multi-tenant DB Containers and Virtualization
Arne Arnold, Ron Silberstein, Dr. Jan Teichmann
SAP HANA Product Management June, 2015
Remark: Realized in the time frame of SPS10

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2Customer
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP.
SAP has no obligation to pursue any course of business outlined in this presentation or to develop or
release any functionality mentioned in this presentation. This presentation and SAP's strategy and
possible future developments are subject to change and may be changed by SAP at any time for any
reason without notice.
This document is provided without a warranty of any kind, either express or implied, including but not
limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement. SAP assumes no responsibility for errors or omissions in this document, except if such
damages were caused by SAP intentionally or grossly negligent.

What is this about?
• SAP HANA provides built-in multi-tenant support,
whereas every database tenant represents a dedicated share of an SAP HANA instance data,
configuration, user management and properties.
• A viable alternative to DB tenants is the use of virtualization technology,
to host multiple isolated SAP HANA instances on one or more servers, enabling each database
instance to appear to run on a separate machine
• Both options offer customers reduced TCO
and additional options for planning and managing their system landscapes.
It also impacts CAPEX positively and hence can for example help to lower the entry barriers for
SMEs and startups to utilize SAP HANA within their business.
• SAP HANA in the Cloud
comes with no CAPEX but OPEX only, operated in dedicated or shared environments, being the
lowest entry-barrier variant

Schema X
SAP HANA Instance
App X
Schema Y
App Y
HW
OS
Database
Multiple Components,
one Database (MCOD)
Schema X
Database
SAP HANA Instance
App X
Schema Y
App Y
Database
SAP HANA Instance
Hypervisor
HW
OS OS
Multiple Components / Instances,
one System (MCOS, Virtualization)
Multi-tenant Database Containers,
one HANA Instance (MDC)
SAP HANA multi-tenancy options
Horizontal View
See Notes 1661202 + 1826100 See SAP Notes 1788665 + 1681092 See SAP Note 2096000
Cloud
SAP HANA MDC enabled Instance
Schema X
Tenant DB
App X
Schema Y
App Y
Tenant DB
HW
OS

Why is this important?
 Cloud-affine SAP HANA Multi-tenant DB Containers capabilities
– Elasticity (shrink and grow tenants, move tenants)
– Security (Separation of provider and customer)
– Optimized for many small tenants (footprint reduction)
– More HW efficiency

SAP HANA Platform
Cloud Options
Status & Outlook

“I want to run my
enterprise applications in
the cloud to…”
“I want to build or extend
an application without
procuring separate tools or
infrastructure…”
SAP HANA
ENTERPRISE CLOUD
SAP Business Suite
powered by SAP HANA
SAP BW
Suite on HANA
SAP HANA CLOUD
PLATFORM
Developer Tools &
Services
Analytics
& Social
HANA DB &
Infrastructure
UX Integration
S/4HANA
SAP Cloud, powered by SAP HANA
COMPLEMENTARY OFFERINGS
“I want to leverage <3rd
Party IaaS> global and
mature IaaS for SAP and
3rd-Party products…”
SAP HANA on 3rd
Party IaaS
IaaS for everything
100%
coverage
Best-in-class
self-service
∞ scalability Openness

Run SAP HANA – and solutions powered by SAP HANA – in a flexible,
secure, and scalable enterprise-class, private cloud
SAP HANA Enterprise
Cloud
APPLICATION
MANAGEMENT SERVICES
SECURITY
ENTERPRISE
APPLICATIONS
SAP HANA
INFRASTRUCTURE &
CLOUD MANAGED
SERVICES
SAP HANA Enterprise Cloud
“Have SAP Run my SAP”
ISO Certificates
 ISO9001 Quality Management System
 ISO27001 Information Security Managem’t System
SOC1 (ISAE3402/SSAE16)
SOC 2 & SOC 3 *)
• SAP’s SLA (ENTIRE solution stack)
Infrastructure, OS, DB, HANA DB, and Application
• Guaranteed standard availability 99.5%
• Global support 24 x 7
• SAP HANA DB Management – Backups, Upgrades,
Monitoring, Restore and Recovery, HA, DR

SAP HANA Cloud Platform
Enabling to build and run business applications in the cloud.
Build
New Cloud Apps
Extend
Cloud Apps
Extend
On-Premise Apps
The in-memory Platform-as-a-Service (“PaaS”) offering from SAP
http://hcp.sap.com/
XSJS

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 11Public
SAP HANA Availability in Public 3rd Party IaaS Cloud
New Cloud Provider, New Options
SAP HANA in certified 3rd Party Cloud
● SAP HANA BYOL on public IaaS
o OLTP and OLAP
o Single node + Scale-out up to 5 nodes 17 nodes if sizing permits, see SAP note 1964437
o Subscription to 3rd party infrastructure, Bring-Your-Own-License (BYOL) for SAP HANA (+ BW, Suite…)
● SAP HANA Developer Edition
o For product evaluations, trials, students, data exploration projects, etc.
o Software is free, developers pay cloud provider for server usage
o Community supported through http://saphana.com/cloud
● SAP HANA One
o Subscription to infrastructure and HANA license
o Non-production and production usage, up to 60.5 GB
o With community support according SAP Note 1798212
3rd Party
3rd
Party
Software
(More coming soon)
* SAP HANA IaaS Certification: mandatory business-case driven process with global reach

SAP HANA Cloud – SPS10 Features With High Impact On Cloud
New Features For Cloud Operations
Improved Cloud (massive-scale) data center support
 Two types of delta backups: Incremental and differential
 Reduction of startup times: rebuild of secondary indexes during reactivation of the RowStore now can be
decoupled / done asynchronously in background
 Integration of SAP HANA Dynamic Tiering into Host Auto-Failover HA capabilities
 Simplified certificate management for SSL/TLS and single sign-on: storing certificates in the database simplifies
the configuration and makes certificate management available to tenant administrators. This is especially
relevant for cloud scenarios where tenant administrators usually do not have access to the file system.
 Multiple Database Container (MDC)
– Extended tenant isolation (OS user / group per tenant DB)
– TREXnet isolation (internal communication, statement permission)
Developer focus
 WebIDE: Close feature gap with HANA Studio

SAP HANA Cloud Platform
News in 1st HY 2015
 SAP HANA
– Installation of new SAP HANA components via HCP cockpit
– Self-service upgrade of SAP HANA installed software components
– SPS09 Rev 91 available since Jan 29th, SPS09 Rev 96 since June 18th
– First accounts using MDC available since June 4th in private beta
 SAP HANA Cloud Platform Internet of Things (IoT) Services (beta)
 SAP JAM integration
 Gamification Service (beta)
 SAP Fiori, Demo Cloud Edition
 New Extension content for SAP JAM, SAP Cloud 4 Customer, S/4HANA
 Improvements in tools and services (Cockpit, Document Service, SAPUI5 through Akamai, Applications on Custom
Domains, UI Theme Designer,…)
 …
See this SAPPHIRE blog and these Release Notes

SAP HANA Platform
Multi-tenant DB Containers
Status & Outlook

SAP HANA Multitenant Database Containers (MDC)
Summary
Multitenant Database Containers provide strong isolation capabilities
 Each tenant database has its own database admin and end users, database catalog,
repository, persistence, backups, traces and logs
 Tenants Memory and CPU consumption can be configured independently
 Integration with SAP HANA data center operation procedures, housekeeping,
backups (full and/or on tenant level), etc.
Multitenant Database Containers share one SID and Revision
 Shared installation of database system software
 Tenant databases are identified by name or port
 SAP HANA system replication covers whole system (Sys. DB and tenants)
 Additive sizing for all tenant database
Targeting MCOS-like on premise and SAP HANA cloud platform
scenarios with a reasonable number of tenant databases per system.
Application
SAP HANA System
Tenant DB
Application
Tenant DB
System DB

SAP HANA Platform
HANA Workload Management
Workload Management
• Automated balancing between complex
and long running queries vs. simple &
short running ones
• Allow for HW resource consumption
limits (CPUs, threads, memory) per
instance / per DB user
• Privileged processing in Emergency
Support Mode (through separate
connection to the SAP start service)
SAP HANA Multi-tenant DB Containers
• Strong isolation capabilities between tenants
• Lower TCO, single software stack, central
configuration & administration
• Performance optimized federation / cross-
schema access through Smart Data Access
(SDA)

PLANNED INNOVATIONS Future DirectionToday
This is the current state of planning and may be changed by SAP at any time.
(SAP HANA SPS09) (planned for SAP HANA SPS10)
SAP HANA Platform
Multitenant Database Containers Roadmap
 Multiple containers in one HANA system
– Individual and isolated databases
– Central topology administration
– One HANA version / One HA/DR setup
 Isolation
– Separate data files
– Separate schemas and users
– Individual encryption keys
– Individual backup
 Cross Database Access
– Based on SQL (read only)
– Reduced set of objects
– Multi-layered authorization
 Load Management
– Static load control (CPU, Memory)
 Product Readiness
– Extended features for backup and
recovery
– Feature extensions for cross database
access (read access)
 Cloud Readiness
– Extended tenant isolation
– TREXnet isolation (internal
communication, statement permission)
 GUI Support for MDC
– HANA Cockpit,
– SAP Database Control Center
 Quality hardening
– Extended testing
– Integration test: Dynamic Tiering and
Smart Data Streaming
 License management
 individual tenant licences
 Tenant cardinality
 reduce memory footprint
 Tenant copy & move
 manage tenant landscape
 Cross Database Access
 Extend functionality (e.g. write
transactions)
 Extend Admin UI support
 HANA Cockpit, Database Control Center

PLANNED INNOVATIONS Future DirectionToday
(SAP HANA SPS09) (planned for SAP HANA SPS10)
SAP HANA Platform
HANA Workload Management Roadmap
 Emergency Connection
 Resource Management for
Memory
 Resource Management for CPU
 Priorities for statement
execution
 Mixed OLAP / OLTP workload
handling optimization
 Automated workload
management mechanisms
(CPU+Memory)
 Workload classes: provides
more granular controls for
workload management features
 Further improvements for
internal automated workload
management mechanisms
(mixed workloads)
 NUMA-aware workload
management
 Dynamic workload management
(inter-process)
 Ongoing NUMA-aware workload
management
 Consider additional context
information for workload
management (e.g. locking)
 …

SAP HANA Platform
other options for multi-tenancy
Support Status & Outlook

SAP HANA partitioned
Currently Supported HW Partitioning Technology
• In addition to MCOS and MCOD deployment options …
… which may also be considered to achieve multi-tenant like environments.
See SAP Note 1681092 for specific information and constraints.
• … the currently supported HW partitioning technology for running SAP HANA are:
• General support for HP nPartitions in context of HP CS 900 with Superdome X servers
for production and non-production use cases.
See SAP Note 2103848 for more specific information and constraints.
• General support for Fujitsu physical partitioning with PRIMEQUEST 2400 E/L and PRIMEQUEST 2800 E/L
for production and non-production use cases
See SAP Note 2111714 for more specific information and constraints.

SAP HANA virtualized
Currently Supported Hypervisors / Logical Partitioning Technology
• VMware vSphere 5.1 with SAP HANA SPS 05 or later for non-production use cases
• VMware vSphere 5.5 with SAP HANA SPS 07 or later for production and non-production use cases
• In General Availability for single-VM scenarios.
See SAP Note 1995460 for specific information and constraints
• In Controlled Availability for multi-VM scenarios.
Note, that access to this SAP Note is restricted to customers participating in the controlled availability phase.
• In Controlled Availability for SAP BW, powered by SAP HANA scale-out scenarios.
• Hitachi LPAR 2.0 with SAP HANA SPS 07 or later for production and non-production use cases
• In Controlled Availability for single- and multi-VM scenarios.

Controlled Availability Application Process
• Customers interested in running …
• multiple SAP HANA VMs on VMware vSphere 5.5 in production
• SAP BW, powered by SAP HANA on VMware vSphere 5.5. in scale-out and production
• one or more SAP HANA VMs on Hitachi LPAR 2.0 in production
… can apply for Controlled Availability of SAP HANA production support by sending an email to:
sap_hana_tailored_data_center_integration@sap.com
• This email should contain…
• High-level scenario description and timeline (e.g. planned Go-live date)
• Expected database size (compressed HANA DB size, number of users)
• Hardware spec (HW vendor, server t-shirt size),
• Planned HA/DR setup (if applicable),
• Contact details (if possible incl. SAP account number) for further communication
All information provided will be kept confidential and is only used during the selection process. Once accepted, customers will
receive the usual SAP HANA support as also provided for non virtualized environments for the presented scenario.

Currently Supported Hypervisors / Logical Partitioning Technology
The following general constraints and conditions do apply while running SAP HANA virtualized:
• Configuration and overall setup complies with the current version of the "SAP HANA Guidelines for being virtualized" and
the vendor specific best practice documents for running SAP HANA in a virtualized environment on corresponding
hypervisor.
• Each SAP HANA instance / virtual machine needs to be sized according to the existing SAP HANA sizing guidelines and
corresponding hypervisor vendor recommendations. CPU and memory over-provisioning must not be used.
• Beside "SAP BW, powered by SAP HANA in scale-out", the maximum size of a virtual SAP HANA instances is limited by
the maximum size the hypervisor supports per virtual machine and the application dependent core-to-memory ratios.
• The SAP HANA system setup needs to be done by an SAP HANA certified engineer, on SAP HANA certified hardware, and
successfully verified with the SAP HANA hardware configuration check tool (SAP HANA Tailored Datacenter Integration
option). Alternatively, the system can be delivered pre-configured with hypervisor and SAP HANA software installed by SAP
HANA hardware partner (SAP HANA appliance option).
• Nested virtualization (running a hypervisors within another hypervisor stack) is not supported by SAP.
Customers may, however, run virtualized applications on physically separated hardware partitions.

Technology Roadmap (from today to H2/2015+)
Single VM
production
support
Complement
deployment
options
Multi VM
support
(in CA)
GA
BWoH Scale-
out support
(in CA)
GA
Extend
platform
support
vSphere 6
support
8 socket HW
support
Add variety
support for
Hitachi LPAR
Support of
additional
hypervisors
H1/2014 H2/2014 H1/2015 H2/2015+
(CA) Controlled Availability - (GA) General Availability - (BWoH) SAP business Warehouse, powered by SAP HANA
• Today
• General support for SAP HANA on
VMware vSphere 5.1 in non-production
• General support for single SAP HANA VMs
on VMware vSphere 5.5
in production and non-production
• Controlled Availability for multi-VM and
BW on HANA scale-out scenarios on
VMware vSphere 5.5 in production
• Controlled Availability for Hitachi LPAR
(single and multiple partitions) in production
• On Roadmap
 Support of larger VMs (4 TB) and 8-socket
hardware with VMware vSphere 6
 Support for Multi-VM and Scale-Out in GA

Considerations and tradeoffs
• Virtualization is
usually limited in size
and supported
scenarios (e.g. 1 TB
for vSphere 5.5; in
general no-scale out
as of today)
• MDC supports any
size and scenario
• MDC creates
isolation between
tenants - inside one
DBMS
• Virtualization & HW
Partitioning offers
isolation down to
OS-level
• MDC can handles
HW resource
management
internally the
database
• Virtualization & HW
Partitioning can
only balance
workload without
application
knowledge (outside /
black-box view)
• Virtualization adds
another technology
layer which may
required licenses
and knowledge.
• A virtual SAP HANA
system may however
also just plug-in into
an existing and fully
virtualized
datacenter.
• HW Partitioning
may introduce
another vendor lock-
in
MDC: SAP HANA Multi-tenant database containers

Further Reading
• SAP HANA Virtualized – Central Note
https://service.sap.com/sap/support/notes/1788665
• SAP HANA Hypervisor – Technology Roadmap
http://scn.sap.com/docs/DOC-60329
• SAP HANA Platform Availability Matrix for SAP HANA certified HW configurations
• SAP HANA HW Configuration Check Tool and corresponding thresholds
https://service.sap.com/sap/support/notes/1943937
• SAP HANA Guidelines for SAP HANA running virtualized

© 2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP HANA SPS10- Multitenant Database Containers

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to SAP HANA SPS10- Multitenant Database Containers (20)

More from SAP Technology (20)

Recently uploaded (20)

SAP HANA SPS10- Multitenant Database Containers