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

# Send your database schema to Devolutions support

Send your database schema to Devolutions support directly from a workspace upgrade tab for database backed Remote Desktop Manager workspaces.

Sometimes the support staff will ask for the database schema.

{% hint style="info" %}
This feature is only available for workspaces that are backed by a database management system like Azure SQL and SQL Server.
{% endhint %}

{% hint style="warning" %}
If you are unable to send your schema to the support staff following the procedure below, please use this workaround. Go to ***File – Workspaces - Edit - Upgrade*** then hold the <kbd>Ctrl</kbd> key and click on ***Email schema to support*** You will then be able to save it locally by pasting it in a text file.
{% endhint %}

1. Go in ***File – Workspaces - Edit workspace***.
2. In the ***Upgrade*** tab click on ***Email schema to support***.
3. Fill in your information and click on ***Send***.


---

# 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/rdm/knowledge-base/how-to-articles/send-your-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.