> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/managing-services.md).

# Managing services

Core lifecycle actions — **Stop**, **Edit**, and **Delete** — are accessible from two places: the ellipsis icon (︙) on the My Services dashboard row, and the ellipsis icon on the database service home page.

***

## How do I stop a database service?

All active sessions are disconnected. Status transitions from **Stopping** → **Stopped**. Once stopped, the ellipsis icon shows a **Start** option to restart the service.

* If there is only one service on the VM, both the database and the VM are stopped.
* In a multi-service deployment, only the database is stopped; the VM keeps running.

> **Note:**
>
> * Stop is unavailable when **stop protection** is enabled on the service.
> * Stop is not allowed when a DR instance is attached to the service. Because DR uses asynchronous replication, stopping the primary could break replication continuity.
> * Use stop to reduce costs during development, testing, or training periods when the database is not needed.

### Steps to stop a service

1. Click the ellipsis icon (︙) next to the service → select **Stop**.
2. Optionally add comments explaining the reason.
3. Select the **Are you sure you want to continue?** checkbox.
4. Click **Stop**.

***

## How do I edit a database service?

The Edit service dialog lets you update:

| Setting                              | Description                                                                                                   |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Service name**                     | Rename the database service                                                                                   |
| **Description**                      | Update the free-text description                                                                              |
| **Enable delete protection**         | When enabled, blocks deletion to prevent accidental data loss (disabled by default)                           |
| **Enable stop protection**           | When enabled, blocks the Stop action (disabled by default)                                                    |
| **Enable auto minor version update** | When enabled, automatically applies minor Oracle patches as they are released by Tessell (enabled by default) |

### Steps to edit a service

1. Click the ellipsis icon (︙) → select **Edit**.
2. Make the required changes in the **Edit service** dialog.
3. Click **Update**.

***

## How do I delete a database service?

Deletion is permanent and irreversible. You control whether the Availability Machine (snapshots, transaction logs, DAPs) is retained after the service is deleted.

> **Note:** Delete is unavailable when **delete protection** is enabled on the service.

### Steps to delete a service

1. Click the ellipsis icon (︙) → select **Delete**.
2. (Optional) Select **Take a final snapshot before deletion** to create a standalone manual snapshot immediately before deletion.
   * Specify a name in **Snapshot Name**, or use the auto-generated name.
   * This snapshot is independent of the Availability Machine and is retained even if you do not retain the Availability Machine.
   * A final snapshot does **not** support PITR, because PITR requires the transaction log chain that is not preserved with this option.
3. Choose how to handle the **Availability Machine**:

   | Option                                                      | What is retained                                                                                                                                                                                                                                                                                 |
   | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
   | **Retain existing data** → All existing data                | Full Availability Machine (snapshots, backups, transaction logs, DAPs) retained and aged out per the RPO policy. Azure/AWS NetApp Files volumes are also retained.                                                                                                                               |
   | **Retain existing data** → Starred snapshots & backups only | Only starred snapshots and backups are kept; all other snapshots, transaction logs, and DAPs are deleted. For more information, see [How do I star or unstar a snapshot?](/tessell/database-engines/tessell-for-oracle/db-services/availability-machines.md#how-do-i-star-or-unstar-a-snapshot). |
   | **Do not retain** (checkbox cleared)                        | Availability Machine and all its contents — snapshots, DAPs, logs — are deleted across all regions.                                                                                                                                                                                              |
4. Optionally, add comments.
5. Type the exact service name in the confirmation field.
6. Click **Delete**.

### VM deletion behaviour

| Deployment type       | What is deleted                                                                                                                                           |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Single-service VM** | Both the database service and the underlying VM are deleted.                                                                                              |
| **Multi-service VM**  | Only the database service and its storage are deleted; the VM remains. Delete the VM from the **Servers** app after all databases on that VM are removed. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/managing-services.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.