> 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/prevent-sql-timeouts.md).

# Undgå SQL-timeouts

Undgå SQL-timeouts i Devolutions Server ved at justere puljestørrelsen for databaseforbindelser, forbindelsestimeout og antallet af gentagne forbindelsesforsøg.

Administration af mange poster i én enkelt handling eller et højt antal forbundne brugere kan føre til fejlmeddelelser om SQL-timeout med Devolutions Server. Følgende ændring af databasens avancerede parametre kan hjælpe med at undgå SQL-timeouts.

1. Den første, De bør overveje, er ***Maksimal puljestørrelse for forbindelser*** Hvis parameteren øges til 1000 i stedet for standardværdien 100, hjælper det med at hæve antallet af mulige databaseforbindelser.
2. Den anden parameter er ***Forbindelsestimeout***, som kan øges til 30 sekunder. Dermed venter systemet 30 sekunder, før der udløses en undtagelse.
3. Den sidste er ***Antal gentagne forsøg på forbindelse***, da den gentager hver forsinkelse for ***Forbindelsestimeout***, før der genereres en fejl. Hvis den sættes til 5, venter instansen af Devolutions Server 150 sekunder, før der udløses en SQL-timeout.

Hvis De vil have flere oplysninger om disse parametre, kan De se [Database – avancerede indstillinger](/server/da/devolutions-server-console/devolutions-server-settings/database/advanced-settings.md).


---

# 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/prevent-sql-timeouts.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.