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

# Gruppi di disponibilità Always On di SQL Server

Verifichi quali configurazioni dei gruppi di disponibilità SQL Server Always On sono supportate da Remote Desktop Manager e Devolutions Server tramite i loro driver di database.

I client principali di Remote Desktop Manager e Devolutions Server sono sviluppati sulla piattaforma .NET. Pertanto, le loro funzionalità relative al database dipendono spesso dalle librerie .NET sottostanti.

Di conseguenza, i gruppi di disponibilità supportati dipendono dalle funzionalità fornite dal driver di database stesso. I seguenti tipi sono tutti supportati:

* Application intent
* Failover multi-subnet
* Failover multi-subnet: failover più rapido degli endpoint in una singola subnet
* Failover multi-subnet: risoluzione delle istanze denominate per le istanze cluster di SQL
* Routing di sola lettura


---

# 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/it/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.