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

# Générer un script pour les permissions de base de données

Générez un script SQL dans la console Devolutions Server pour accorder des permissions de base de données aux comptes du service du planificateur et de l'application web.

Les instructions suivantes présentent la méthode pour générer un script SQL afin d'accorder des permissions aux comptes utilisés pour communiquer avec la base de données SQL. Les fichiers scriptsql peuvent être générés pour le compte du service du planificateur et le compte de l'application web. Pour en savoir plus sur ces comptes, consultez cet article de la base de connaissances sur le [Sondage des comptes avant le déploiement](/server/fr/knowledge-base/knowledge-base-articles/pre-deployment-account-survey.md).

Pour accéder à ce dialogue :

1. Depuis la console Devolutions Server, modifiez l'instance Devolutions Server.
2. Allez dans l'onglet ***Base de données***.
3. Cliquez sur le bouton ***Identifiants avancés***.
4. Cliquez sur la flèche à côté de l'un des boutons ***Appliquer les permissions minimales***.
5. Cliquez sur le bouton ***Générer un script*** pour enregistrer le fichiersql.


---

# 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/fr/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.