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

# Generare uno script per le autorizzazioni del database

Generi uno script SQL nella Devolutions Server Console per concedere le autorizzazioni al database agli account del servizio Scheduler e dell'applicazione web.

Le istruzioni seguenti forniscono il metodo per generare uno script SQL che conceda le autorizzazioni agli account utilizzati per comunicare con il database SQL. I file scriptsql possono essere generati per l'account del servizio Scheduler e per l'account dell'applicazione web. Per questi account, consulti questo articolo della knowledge base su [Pre-Deployment Account Survey](https://docs.devolutions.net/server/it/knowledge-base/knowledge-base-articles/pre-deployment-account-survey.md).

Per accedere a questa finestra di dialogo:

1. Dalla Devolutions Server Console, modifichi l'istanza di Devolutions Server.
2. Vada nella scheda ***Database***.
3. Clicchi sul pulsante ***Advanced Credentials***.
4. Clicchi sulla freccia accanto a uno dei pulsanti ***Apply Least Permissions***.
5. Clicchi sul pulsante ***Generate Script*** per salvare il filesql.


---

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