SAP HANA Cloud Central: Administration and Monitoring Guide

SAP HANA Cloud Central is the primary web interface for managing the lifecycle and operational settings of SAP HANA Cloud instances. It helps administrators provision instances, review instance status, access service details, and open related administration tools from a central location.

For database-level work, administrators typically use SAP HANA database explorer. The two tools serve different purposes: Central focuses on the cloud service and instance, while database explorer provides SQL-based access and database administration capabilities.

01What SAP HANA Cloud Central does

SAP HANA Cloud Central provides a service-oriented view of the SAP HANA Cloud resources associated with an SAP BTP account. Depending on the account permissions and service configuration, administrators can use it to:

• Create or provision an SAP HANA Cloud instance
• View instance status and service details
• Start or stop an instance when the available controls and plan support the operation
• Open connection information and related tools
• Review capacity, service plan, and instance configuration
• Access operational actions for maintenance and administration

The exact actions available depend on the user’s authorizations, the service plan, and the configuration of the instance. SAP HANA Cloud is sized by instance, service plan, and capacity, so administrators should review those factors together when planning resources.

02Central and database explorer

SAP HANA Cloud Central and SAP HANA database explorer complement each other rather than replacing one another. Central manages the cloud service context, while database explorer is used for database connections and database-oriented tasks.

To understand the database explorer workflow in more detail, see SAP HANA Cloud database explorer. Use Central when the task concerns the instance as a cloud service, and use database explorer when the task concerns objects or activity inside the database.

03Provisioning an instance

Provisioning begins with selecting the appropriate SAP HANA Cloud service and configuring the instance. The important decisions include the service plan, available capacity, cloud region, connectivity requirements, and administrative settings.

Before provisioning, confirm that the BTP account has the required entitlement and that the administrator has suitable permissions. Capacity planning should consider workload size, memory requirements, expected concurrency, data growth, and any compute or storage options available for the selected service configuration.

After the instance is created, record its connection information and validate access through SAP HANA database explorer. A successful connection test confirms that the required network path, credentials, and client configuration are working.

For a broader overview of the setup sequence, see SAP HANA Cloud provisioning.

04Monitoring instance status and performance

Central gives administrators a convenient place to check whether an instance is available and to review service-level information. Performance investigation usually requires additional database-level context, such as workload activity, memory consumption, expensive statements, and active sessions.

A practical monitoring routine starts with the instance status and then moves to database metrics. Check for recent changes in workload, resource consumption, connectivity, and scheduled operations before drawing conclusions from a single metric.

Alerting should be designed around meaningful thresholds and operational impact. For example, an alert for sustained memory pressure may require a different response from an alert caused by a short-lived workload spike. Review SAP HANA Cloud alerts when building a notification and response process.

05Starting and stopping instances

Starting or stopping an instance is a lifecycle operation that can affect application availability and scheduled jobs. Confirm the business impact before taking action, and communicate the expected interruption to application owners when necessary.

Stopping an instance can be useful for supported nonproduction scenarios, maintenance windows, or cost-control practices. Before stopping it, check for active users, integrations, batch jobs, replication activity, and dependent applications. After starting it again, verify the instance status, connectivity, application behavior, and scheduled processing.

The available controls and behavior can vary by service configuration. Use SAP HANA Cloud start and stop for a focused operational checklist.

06Security and access considerations

Access to Central is governed by SAP BTP authorizations and the permissions assigned to the administrator. Access to database objects and SQL operations is governed separately through database users, roles, and privileges.

Apply least-privilege access for both layers. A user who can view or manage an instance does not automatically need broad access to application schemas, sensitive data, or administrative SQL operations. Review role assignments regularly and remove unused access.

Connection credentials should be stored and transmitted securely. When administrators share connection details for troubleshooting, they should avoid exposing passwords, private keys, or other sensitive values in tickets and chat messages.

07A practical administration workflow

A repeatable workflow reduces operational errors:

1. Sign in with an account that has the required SAP BTP and SAP HANA Cloud permissions.
2. Open SAP HANA Cloud Central and select the relevant instance.
3. Review status, service plan, capacity, and recent operational context.
4. Choose the appropriate lifecycle or configuration action.
5. Confirm the effect on applications, integrations, and scheduled jobs.
6. Use SAP HANA database explorer for database-level validation.
7. Record the change, result, and any follow-up monitoring requirement.

This separation of responsibilities makes troubleshooting clearer. Central answers whether the cloud service and instance are in the expected state; database explorer helps determine whether database activity, objects, users, or SQL workload explain the observed behavior.