> 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/de/getting-started/installation/database-setup/database-instance.md).

# Datenbankinstanz

Die Anforderungen an die Devolutions Server-Datenbankinstanz umfassen die SQL Server-Konnektivität und die Konfiguration von Domänen-Single Sign-On nach der Erstellung der Serverinstanz.

Devolutions Server stellt keine Anforderung, die vorgibt, welches Kommunikationsprotokoll verwendet wird, sowie viele der Optionen, die Ihnen von der gewählten SQL Server-Instanz angeboten werden. Solange die Client-Arbeitsstation eine Verbindung zur SQL-Instanz herstellen kann, wird Devolutions Server effektiv laufen. Bitte konsultieren Sie die Microsoft-Dokumentation, um die Konnektivität zur Instanz zu ermöglichen.

Bitte konsultieren Sie [Devolutions Server für die Verwendung von Domänen-Single Sign-On (SSO) konfigurieren](https://docs.devolutions.net/server/de/knowledge-base/how-to-articles/configure-domain-single-sign-on-sso.md) für Anweisungen, die nach der Erstellung der Devolutions Server-Instanz durchgeführt werden müssen.


---

# 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/de/getting-started/installation/database-setup/database-instance.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.
