> 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/da/knowledge-base/how-to-articles/generate-a-script-for-database-permissions.md).

# Generer et script til databasetilladelser

Generer et SQL-script i Devolutions Server Console for at give databasetilladelser til kontoen for planlægningstjenesten og webprogrammets konto.

Følgende vejledning beskriver metoden til at generere et SQL-script, der giver tilladelser til de konti, der bruges til at kommunikere med SQL-databasen. Sql-scriptfilerne kan genereres for kontoen til planlægningstjenesten og kontoen til webprogrammet. For disse konti kan De se vidensbaseartiklen om [Kontoundersøgelse før udrulning](/server/da/knowledge-base/knowledge-base-articles/pre-deployment-account-survey.md).

Sådan kommer De til denne dialogboks:

1. Rediger Devolutions Server-instansen fra Devolutions Server Console.
2. Gå til fanen ***Database***.
3. Klik på knappen ***Avancerede legitimationsoplysninger***.
4. Klik på pilen ved siden af en af knapperne ***Anvend mindste tilladelser***.
5. Klik på knappen ***Generer script*** for at gemme sql-filen.


---

# 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/da/knowledge-base/how-to-articles/generate-a-script-for-database-permissions.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.