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

# Send the Devolutions Server database schema to Devolutions support

Export the database schema of a Devolutions Server instance from the console and send the resulting XML file to Devolutions support for troubleshooting.

Sometimes the support staff will ask for the Devolutions Server database schema. The following procedure describe how to export the database schema of your Devolutions Server instance.

### Steps

1. Select the Devolutions Server instance in the Devolutions Server Console and click on the Edit button.
2. Select the Database tab.
3. Click on the Save Schema button.
4. Select the destination folder and set the file name.
5. Click on Save button.
6. Send us the database schema XML file to <service@devolutions.net>.

#### See also

* [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/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.