Skip to end of metadata
Go to start of metadata


With SAP HANA 1.0 SPS09 the feature 'SAP HANA multitenant database containers' is introduced.

The concept is based on having one single system with a system database that keeps the system-wide landscape information and which allows configuration and monitoring of the overall system. In addition there will be 0 to n tenant databases that are, with regards to application data and user management, strictly isolated from each other (except running on the same hardware in the same instance). Users of one tenant database cannot connect to other tenant databases and neither access application data there (unless the system is enabled for cross database access). All tenant databases can be backed up and recovered independently from one another.

Note: All tenant databases are running with the same SAP HANA software version and the same HA/DR method.

Migration towards a 'SAP HANA multitenant database containers'

SAP HANA single database system can be migrated to a multitenant database system. This step is irrevocable.

Single DB is the SPS09 default, MDC is optional. Upgrading to SPS09 will not change the system mode.

If a migration is explicitly launched, the single database will be converted into a tenant database.
During this process the so called system database, responsible for the system topology, will be generated. There will be no changes to application/customer data.
Additional tenant databases can be added to the system afterwards.

Systems that will provision the content for a new tenant (as a backup) have to be on SPS09 and have to be migrated to MDC before taking the backup. Such backup then can be restored to a tenant in the target MDC system. All other tenants of the target MDC system may operate online, independent from the restore.

A sample pattern to move a single db into an MDC tenant would be:
1.create a copy of your source system
2.migrate this copy to a revision enabled for MDC (>= SPS09 rev95 recommended), if not already there
3.migrate this copy to an MDC system - will result in a system db and one tenant db
4.take a tenant backup from this tenant
5.set up your target tenant, by creating a new tenant in a new or an already existing MDC system
6.restore the tenant backup (from 3.) into this new tenant

Current restrictions (i.e. working with MDC but with restrictions)

There's an issue if the MDC system is set up for system replication. Please check note 2184218.

In a Host Auto-Failover setup the failover might not succeed in a scale-out MDC system; see 2191313 for detail (tenants have to be restarted after failover).

Currently the backup history of an MDC tenant db breaks when a service (dp, xs, ...) is added to or removed from its topology. Thus a new history has to be started for this tenant by taking a complete data backup.

Restrictions exist for the use of SAP HANA Application Lifecycle Management with MDC; see note 2073243 for the latest information.

SAP HANA Dynamic Tiering - requires one DT host per tenant DB. Refer to DT material for further restriction info.

Backup and recovery using snapshots is not yet available for MDC.


Related Content

See the following blog explaining the converting process:

Convert to a Multitenant Data Base


See section titled "Multitenant Database Containers" of the SAP HANA Administration Guide

Related Videos

SAP HANA Academy -Multitenant Database Containers: Overview [SPS 09]

Related SAP Notes/KBAs

SAP Note 2101244 - FAQ: SAP HANA Multitenant Database Containers (MDC)

SAP Note 2141670 - Backup & Restore from a single tenant database into one tenant of a multitenant database fails

SAP Note 2096000 - SAP HANA multitenant database containers - Additional Information





  • No labels


  1. Hello

    full system dump working for me,

    FullSystemInfoDump is not working on tenants, only from the systemdb for all tenants

    Use of command python -t <Tenant SID> will work,



    1. Thanks Sadiq! We have already updated the Wiki content ! And from HANA studio, we could also collect the full system dump directly.