> 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/troubleshooting-articles/sql-server-performance-troubleshooting.md).

# Fejlfinding af SQL Server-ydeevne

Forbedr langsom ydeevne for SQL Server-forespørgsler i Remote Desktop Manager ved at kontrollere størrelsen på transaktionslogfilen og undtage VPN-trafik fra firewallinspektion.

Når ydeevnen for forespørgsler mod SQL Server falder, skal De kontrollere følgende:

### Størrelse på databasefiler

Hvis Deres transaktionslogfil er enorm, kan det skyldes, at databasens gendannelsesmodel er sat til FULL, hvilket betyder, at der kræves regelmæssige sikkerhedskopier for at rydde op i tidligere transaktioner.

De kan bekræfte det i egenskaberne for selve databasen.

Det mest presserende trin er at udføre en fuld sikkerhedskopi af databasen.

Kør følgende sætning mod databasen:

***exec sp\_spaceused***

### VPN

Hvis De arbejder gennem en VPN, kan firewallen opfatte forbindelsen som en UDP-oversvømmelse og tro, at den er under angreb. Det gør alt betydeligt langsommere.

Som en midlertidig løsning kan De sætte VPN'en på en undtagelsesliste.


---

# 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/troubleshooting-articles/sql-server-performance-troubleshooting.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.