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

# Instancia de base de datos

Los requisitos de la instancia de base de datos de Devolutions Server abarcan la conectividad con SQL Server y la configuración del inicio de sesión único (SSO) de dominio después de crear la instanci

Devolutions Server no impone ningún requisito que determine qué protocolo de comunicación se utiliza, así como tampoco muchas de las opciones que le ofrece la instancia de SQL Server elegida. Siempre que la estación de trabajo cliente pueda conectarse a la instancia de SQL, Devolutions Server funcionará correctamente. Consulte la documentación de Microsoft para permitir la conectividad con la instancia.

Consulte [Configurar Devolutions Server para usar el inicio de sesión único (SSO) de dominio](/server/es/knowledge-base/how-to-articles/configure-domain-single-sign-on-sso.md) para conocer las instrucciones que deben ejecutarse después de crear la instancia de Devolutions Server.


---

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