> 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/es/knowledge-base/knowledge-base-articles/data-report.md).

# Informe de datos

Configure una entrada de Informe de datos en Remote Desktop Manager para permitir que los usuarios ejecuten consultas SQL y generen informes sin acceso directo al servidor.

El tipo de sesión ***Informe de datos*** puede utilizarse para permitir que cualquiera o todos los usuarios generen informes, sin necesidad de concederles acceso al servidor real.

## Configuración

### General

Cree una entrada de Informe de datos y defina la cadena de conexión mediante una de estas opciones:

* Especifique la conexión en la propia entrada.
* Utilice una entrada de credencial.
* Heredada de un elemento principal.
* Solicitar credenciales.

### Parámetros

Especifique los parámetros estableciendo el nombre, el tipo y el valor predeterminado de todos los parámetros.

### Consulta

Introduzca la consulta en la pestaña Consulta, que incluye un cuadro de texto con resaltado de sintaxis SQL y números de línea.

{% hint style="info" %}
Asegúrese de que su DBA configure los grupos de usuarios adecuados y de que cada usuario específico tenga acceso a ellos.
{% endhint %}


---

# 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/es/knowledge-base/knowledge-base-articles/data-report.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.