> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/mariadb/overview/working-with-mariadb.md).

# Working with MariaDB

Although <code class="expression">space.vars.ionos\_cloud</code> DBaaS does not grant superuser access to MariaDB services, you may still view database clusters and perform administrator-level activities.

## DBaaS services offered by IONOS CLOUD

All back-end tasks necessary to keep your database operating at peak efficiency are handled by the <code class="expression">space.vars.ionos\_cloud</code> platform. You can perform the following:

* Database installation via the DCD or the DBaaS API.
* Pre-set database configuration and configuration management options.
* Automated backups with point-in-time restore. Retention is seven days for MariaDB v1, and configurable from 1 to 365 days for MariaDB v2.
* Regular patches and upgrades during maintenance.
* Service monitoring both for the database and the underlying infrastructure.

## Database administration

Tasks related to the optimal health of the database remain your responsibility. These include:

* Optimization
* Data organization
* Index creation
* Statistics modification
* Query optimization by reviewing access plans


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/databases/mariadb/overview/working-with-mariadb.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.