---
title: "Stop, start and restart a database"
description: "Stop a TIR DBaaS database and keep its data, start it again, or restart it to drop all connections and reload its settings."
content_type: "how-to"
product: "tir-dbaas"
platform: "TIR"
url: "/tir/tir-dbaas/how-to/stop-start-and-restart-a-database/"
topic: ["power-and-lifecycle"]
---

# Stop, start and restart a database

Stop a database when it can sit idle for a while. Its data and storage are kept, and
you start it again when you need it. Restart a running database when settings
PostgreSQL reads only at start-up, such as some parameter group values, need to take effect. A
restart drops every open connection.

## Before you begin

- A database in the **Running** state to stop or restart, or in the **Stopped** state to start.
- The update permission for DBaaS in the project. See [TIR Access Control](/tir/tir-iam/).

To find the actions, select **DBaaS** under **Databases** in the side menu. **Stop Database** or
**Start Database**, and **Restart Database**, are in the database's row menu on the **Manage
Databases** list, and in the three-dot menu on its details page. The menu has **Start Database**
when the database is **Stopped**, and **Stop Database** otherwise.

## Stop a database

Stopping drops every open connection, and clients can connect again only once you start the database.

1. Choose **Stop Database**.
2. In the dialog, tick "I understand and want to stop the database" followed by the database's name.
3. Select **Stop**.

The status changes to **Stopped** as soon as TIR accepts the request. The database is powered off,
and its storage is kept.

While the database is **Stopped**:

- **Connect** and **Edit** return once you start the database.
- Scheduled snapshots are skipped. The schedule stays set, and you can still open it and change it.
- You can still restore its snapshots into a new database, and you can delete the database.

## Start a database

1. Choose **Start Database**.
2. Confirm with **Start**.

The status shows **Creating** until PostgreSQL accepts connections, and then **Running**.

## Restart a database

Restarting drops every open connection. Applications need to reconnect once the database is back.

1. Choose **Restart Database**.
2. Confirm with **Restart**.

The database reboots, and the status shows **Creating** until PostgreSQL accepts connections again,
and then **Running**.

To change a parameter group and restart in one step, use **Update & Restart** in **Edit Database**.
See [Edit a database](/tir/tir-dbaas/how-to/edit-a-database/).

## When an action is refused or fails

If TIR refuses the action, it gives the reason, such as the database needing to be **Running**
first. Wait until the database has the status the action needs, then try again.

If a start or restart fails to complete, the database turns **Failed** and TIR raises a support ticket
for it. **Connection Details** on the **Overview** tab then says that a support ticket was raised
automatically. For what to do next, see [Troubleshooting TIR
DBaaS](/tir/tir-dbaas/troubleshooting/tir-dbaas/).

Each action is recorded on **Activity Timeline** as "Database stopped", "Database started" or
"Database restarted". To remove a database for good, see [Delete a
database](/tir/tir-dbaas/how-to/delete-a-database/).