How to Start and Stop an SAP HANA Cloud Database

01Why start and stop an SAP HANA Cloud database

Starting or stopping an SAP HANA Cloud database is an operational task used to control when the database is available for connections and workload execution. The action is performed for a specific database instance in SAP HANA Cloud Central.

A stopped database does not accept normal application connections or execute workload. Applications, scheduled jobs, integrations, and administration tools that depend on the database can therefore report connection failures until the database is running again. Plan the action around maintenance windows, batch processing, and business availability requirements.

Stopping a database can also help reduce consumption during periods when the instance is not needed, depending on the service plan and current SAP HANA Cloud capabilities. Review the commercial and technical behavior of the selected service plan before using repeated stops as a cost-control practice.

02Before stopping the database

Confirm that no important workload is running. Check active users, application sessions, scheduled tasks, data loads, replication activity, and long-running transactions. A controlled application shutdown is safer than abruptly removing database availability from connected clients.

Record the expected stop window and notify application owners. If the database supports development or test systems, verify that automated pipelines will not attempt deployments or tests while the instance is stopped.

Use SAP HANA Cloud Central to review the instance and its available operations. The database status, service details, and account permissions determine which actions are available to you.

Stopping a database is not the same as deleting it. Stopping preserves the instance and its configuration, while deletion is a separate, destructive lifecycle operation. Confirm the selected action and target instance before proceeding.

03How to stop an SAP HANA Cloud database

1. Sign in to SAP HANA Cloud Central with an account that has permission to manage the relevant SAP HANA Cloud resource.
2. Open the environment, subaccount, or project context that contains the target database.
3. Select the SAP HANA Cloud database instance.
4. Open the instance actions and choose the option to stop the database.
5. Review the confirmation details, including the instance name, and confirm the operation.
6. Wait for the status to change from a running or transitional state to stopped.

The transition may take time. Do not repeatedly submit the same action while the service is processing the request. Refresh the instance view and check the status shown by SAP HANA Cloud Central.

After the database stops, test the expected behavior from a controlled client if needed. A connection failure from an application is expected while the database is stopped; it does not by itself indicate database corruption.

04How to start an SAP HANA Cloud database

1. Open SAP HANA Cloud Central and locate the stopped database instance.
2. Select the instance and open its available actions.
3. Choose the option to start the database.
4. Confirm the requested operation.
5. Wait until the status indicates that the database is running and ready for connections.
6. Reconnect using SAP HANA database explorer or the application connection method used by the system.

Startup has a transitional period. The instance may appear to be starting before it is ready to accept all connections. Allow the status to settle before restarting application services or launching dependent jobs.

Use SAP HANA database explorer to validate connectivity and perform a focused post-start check. Confirm that the expected database user can connect, the required schemas are accessible, and a simple read-only query completes successfully.

05What changes when the database is stopped

Stopping affects availability, not just an administrative display state. Client connections can fail, SQL requests cannot run, and dependent services may enter retry or error states. Applications should use appropriate retry behavior rather than generating uncontrolled connection traffic during the stop interval.

The database instance and its persistent data remain associated with the service. Starting it again does not represent a restore operation. If the goal is to recover deleted, corrupted, or accidentally changed data, use the applicable recovery capabilities rather than the start action.

SAP HANA Cloud sizing is associated with the instance, service plan, and capacity configuration. Stopping and starting should therefore be considered alongside the instance’s capacity requirements and operating schedule, not as a substitute for right-sizing.

06Troubleshoot start and stop problems

If the stop or start action is unavailable, verify that you selected the correct database and that your account has the required resource-management permissions. Also check whether another lifecycle operation is already in progress.

If the status remains transitional for an unusually long time, refresh SAP HANA Cloud Central, note the displayed status and timestamps, and check relevant service notifications. Avoid issuing conflicting lifecycle commands while the first operation is unresolved.

If the database is running but a client cannot connect, investigate the client configuration separately. Check the host, port, authentication method, network access, firewall or allowlist settings, and whether the client is using the correct tenant or database identifier. A successful start does not automatically correct an invalid client configuration.

For monitoring context, see SAP HANA Cloud alerts to review how operational signals can help distinguish availability events from broader service issues.

If users can connect but applications fail, inspect connection pools, expired credentials, deployment dependencies, and application retry behavior. Validate the database independently with a known-good administrative or diagnostic connection before changing application settings.

07Operational checklist

Before stopping:

• Confirm the target instance and planned maintenance window.
• Notify application and integration owners.
• Check for active workloads, transactions, and scheduled jobs.
• Confirm that no deployment or data-load process depends on the database during the window.

After starting:

• Verify that SAP HANA Cloud Central reports the expected running state.
• Test a controlled connection with SAP HANA database explorer.
• Confirm application connectivity and connection-pool recovery.
• Resume scheduled jobs and integrations in the intended order.
• Review monitoring signals for unexpected errors after availability returns.

For capacity planning around operating schedules, compare this procedure with SAP HANA Cloud scaling. Scaling changes capacity; starting and stopping changes service availability, so the two operations solve different operational problems.