> 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/pam/fr/pam-with-devolutions-server/providers/custom-pam-providers/sql-server-login.md).

# Connexion SQL Server

Ce fournisseur PAM personnalisé pour connexion SQL Server automatise la détection de compte, la validation par battement de coeur et la rotation des mots de passe pour les identifiants de connexion SQ

Ce fournisseur PAM personnalisé pour connexion SQL Server est conçu pour s'intégrer au module Devolutions PAM afin de gérer les identifiants de connexion SQL Server. Il permet la détection de compte automatisée et la rotation des mots de passe pour les connexions SQL Server.

Ce fournisseur offre les capacités suivantes :

* **Détection de compte** : énumération automatisée des comptes de connexion SQL Server.
* **Battement de coeur** : validation que les mots de passe stockés dans Devolutions Server correspondent à ceux configurés sur l'instance SQL Server.
* **Rotation des mots de passe** : mise à jour automatisée des mots de passe de connexion SQL Server conformément à la politique ou sur demande.

Le modèle prédéfini pour ce fournisseur PAM personnalisé se trouve [sur GitHub](https://github.com/Devolutions/PAM-Providers/tree/master/Providers/sql_server_login).


---

# 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/pam/fr/pam-with-devolutions-server/providers/custom-pam-providers/sql-server-login.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.