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

# Configuration de la base de données

Cette section explique la configuration de SQL Server pour Devolutions Server, en couvrant la mise en place de l'instance de base de données et la tolérance aux pannes au moyen de topologies actif-pas

Cette section fournit les directives essentielles pour configurer l'instance SQL Server utilisée par Devolutions Server. La sous-section [Instance de base de données](/server/fr/getting-started/installation/database-setup/database-instance.md) présente les exigences de base et les considérations de connectivité afin d'assurer un déploiement réussi, quel que soit le protocole de communication. Pour les scénarios plus avancés, l'article [Tolérance aux pannes au niveau de la base de données](/server/fr/getting-started/installation/database-setup/fault-tolerance-at-the-database-level.md) explique les contraintes de la plateforme et les meilleures pratiques pour mettre en œuvre la haute disponibilité, y compris des recommandations concernant les topologies actif-passif et les raisons pour lesquelles la réplication de base de données ne convient pas au partage de données entre plusieurs équipes.


---

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