> 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/fr/knowledge-base/knowledge-base-articles/sql-server-always-on-availability-groups.md).

# Groupes de disponibilité SQL Server Always On

Découvrez quelles configurations de groupes de disponibilité SQL Server Always On sont prises en charge par Remote Desktop Manager et Devolutions Server par l'intermédiaire de leurs pilotes de base de

Les clients principaux de Remote Desktop Manager et de Devolutions Server sont conçus avec la plateforme .NET. Par conséquent, leurs capacités liées aux bases de données dépendent souvent des bibliothèques .NET sous-jacentes.

Par conséquent, les groupes de disponibilité pris en charge dépendent des fonctionnalités offertes par le pilote de base de données lui-même. Les types suivants sont tous pris en charge :

* Intention de l'application
* Basculement multi-sous-réseau
* Basculement multi-sous-réseau : basculement plus rapide du terminal d'un sous-réseau unique
* Basculement multi-sous-réseau : résolution des instances nommées pour les instances en grappe SQL
* Routage en lecture seule


---

# 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/fr/knowledge-base/knowledge-base-articles/sql-server-always-on-availability-groups.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.