> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/it/knowledge-base/how-to-articles/send-the-devolutions-server-database-schema-to-devolutions-support.md).

# Inviare lo schema del database di Devolutions Server al supporto Devolutions

Esporti lo schema del database di un'istanza di Devolutions Server dalla console e invii il file XML risultante al supporto Devolutions per la risoluzione dei problemi.

A volte il personale di supporto richiede lo schema del database di Devolutions Server. La procedura seguente descrive come esportare lo schema del database della sua istanza di Devolutions Server.

### Passaggi

1. Selezioni l'istanza di Devolutions Server nella Devolutions Server Console e clicchi sul pulsante Edit.
2. Selezioni la scheda Database.
3. Clicchi sul pulsante Save Schema.
4. Selezioni la cartella di destinazione e imposti il nome del file.
5. Clicchi sul pulsante Save.
6. Ci invii il file XML dello schema del database a <service@devolutions.net>.

#### Vedi anche

* [Export your Devolutions Server database schema](https://academy.devolutions.net/student/activity/3056469-export-your-devolutions-server-database-schema)


---

# 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.devolutions.net/server/it/knowledge-base/how-to-articles/send-the-devolutions-server-database-schema-to-devolutions-support.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.
