> 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/da/knowledge-base/how-to-articles/send-your-database-schema-to-devolutions-support.md).
# Send databaseskemaet til Devolutions-support
Send databaseskemaet til supporten hos Devolutions direkte fra fanen Opgrader for et arbejdsområde for databaseunderstøttede arbejdsområder i Remote Desktop Manager.
Nogle gange beder supportmedarbejderne om databaseskemaet.
{% hint style="info" %}
Denne funktion er kun tilgængelig for arbejdsområder, der er understøttet af et databasestyringssystem som Azure SQL og SQL Server.
{% endhint %}
{% hint style="warning" %}
Hvis De ikke kan sende skemaet til supportmedarbejderne ved at følge fremgangsmåden nedenfor, skal De bruge denne midlertidige løsning. Gå til ***Fil – Arbejdsområder - Rediger - Opgrader***, hold derefter tasten Ctrl nede, og klik på ***Send skema til support via e-mail*** De kan derefter gemme det lokalt ved at indsætte det i en tekstfil.
{% endhint %}
1. Gå til ***Fil – Arbejdsområder - Rediger arbejdsområde***.
2. På fanen ***Opgrader*** skal De klikke på ***Send skema til support via e-mail***.
3. Udfyld oplysningerne, og klik på ***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/da/knowledge-base/how-to-articles/send-your-database-schema-to-devolutions-support.md?ask=&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.