SAP HANA Tenant Database: Create, Manage, Rename, and Delete Tenants

SAP HANA 2.0 uses a multitenant architecture with one system database and one or more tenant databases. The system database provides central administration, while each tenant contains its own application data, users, schemas, services, and configuration scope.

This guide explains the main lifecycle tasks for a SAP HANA tenant database, including creation, connection, startup and shutdown, renaming, deletion, and operational checks.

01Understand the tenant database architecture

A tenant database is logically separate from the system database but runs within the same SAP HANA system. The system database manages system-wide functions and provides the central point for tenant administration. Tenant databases serve application workloads and can be administered through SAP HANA cockpit or SAP HANA database explorer.

The system database and tenant databases share the system's underlying installation and host resources. Their separation supports independent application data, database users, backup planning, and operational procedures while retaining centralized system administration.

Use the M_DATABASES view in the system database to list tenant databases and review their database status. Connect to the correct database before running database-specific SQL or changing tenant-level configuration.

02Create a tenant database

Create a tenant database from the system database with a database administrator account. The account needs the DATABASE ADMIN privilege. A SQL statement follows this structure:

CREATE DATABASE DB0 SYSTEM USER PASSWORD Manager1;

Replace the database name and password with values that meet the organization's naming and password policies. Store the initial system-user credentials securely and establish the intended administrative users after creation.

The creation process allocates the tenant's database services and makes the tenant available for further configuration. After creation, confirm the tenant status in SAP HANA cockpit or SAP HANA database explorer, then connect directly to the new tenant to configure users, schemas, application settings, and backup policies.

For the broader installation sequence, see SAP HANA installation. For lifecycle commands and software component management, see the SAP HANA hdblcm guide.

03Start and stop a tenant database

Start or stop one tenant from the system database with the corresponding ALTER SYSTEM statement:

ALTER SYSTEM START DATABASE <name>;
ALTER SYSTEM STOP DATABASE <name>;

Replace <name> with the tenant database name. These statements target one tenant and should be executed in the system database by an account with the required administrative privileges.

The HDB script and sapcontrol operate on the complete SAP HANA system, including all tenant databases. For a local host, the system administrator can use /usr/sap/<SID>/HDB<instance number>/HDB start or /usr/sap/<SID>/HDB<instance number>/HDB stop. In a distributed system, use sapcontrol -nr <instance number> -function StartSystem or sapcontrol -nr <instance number> -function StopSystem with the <sid>adm user. The -nr option identifies the instance number, and -host selects a host when required.

Use SAP HANA cockpit to monitor the tenant's status and review alerts after startup. The SAP HANA start and stop guide provides related system-level operating procedures.

04Rename a tenant database

Renaming a tenant database affects connection strings, application configurations, monitoring rules, backup jobs, scripts, and user procedures. Plan the change during a controlled maintenance window and identify every client that uses the current database name.

Use SAP HANA cockpit or SAP HANA database explorer to perform the supported tenant rename operation from the system database context. Before confirming the operation, verify the target name, check dependent application settings, and ensure that the tenant is in an appropriate operational state.

After the rename, update connection properties, technical users, monitoring definitions, scheduled jobs, backup configuration, and documentation. Test application connectivity and review system database information to confirm that the new name is used consistently.

05Delete a tenant database safely

Deleting a tenant permanently removes the tenant database and its data. Treat deletion as a controlled retirement procedure rather than a routine cleanup task.

Before deletion, obtain the required approval, stop application access, record dependencies, and create or validate the final backup according to the organization's retention policy. Confirm that the backup can be located and that the recovery process is understood before proceeding.

Use SAP HANA cockpit or SAP HANA database explorer from the system database to execute the supported tenant deletion workflow. Confirm the database name carefully and review the operation's impact before committing it. After deletion, remove obsolete connection entries, monitoring objects, scheduled tasks, and credentials.

06Operate tenant databases securely

Apply separate administration and security procedures to the system database and each tenant. Grant only the privileges required for a task, use named administrative accounts, and monitor authentication and authorization events.

Plan data volume encryption, log volume encryption, and backup encryption as separate controls. When encryption is configured or changed, back up the relevant root keys and create another root-key backup after every change. A backup encryption root key that changes without a new backup makes the affected backup unrecoverable.

Include tenant databases in backup and recovery plans, capacity reviews, alert monitoring, and operational testing. SAP HANA cockpit provides centralized visibility, while SAP HANA database explorer is useful for database connections, SQL execution, and database-level inspection.

07Tenant database administration checklist

Use this sequence for a controlled tenant lifecycle:

1. Confirm whether the task belongs in the system database or the tenant database.
2. Verify the administrative account and required privileges.
3. Check the tenant status in M_DATABASES and SAP HANA cockpit.
4. Capture dependencies, connection details, and recovery requirements.
5. Perform the operation during an approved maintenance window.
6. Validate services, application connectivity, monitoring, and backup jobs.
7. Record the final database name, status, owners, and operational evidence.

A clear separation between system-level and tenant-level actions prevents accidental changes to other databases and supports repeatable SAP HANA administration.