> For the complete documentation index, see [llms.txt](https://doc.velneo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.velneo.com/22/velneo-vdevelop/buenas-practicas-de-programacion/buenas-practicas-de-rendimiento/buenas-practicas-base-de-datos/puntero-indirecto-real-vs-virtual.md).

# Puntero indirecto real vs virtual

![](/files/-M7D7RpTX2h07dm7IQWk)

## Virtual más rápido en escritura

El puntero indirecto virutal es notablemente más rápido que el real en escritura, dando altas de registros. En lectura es algo más lento que el real, pero la diferencia no es muy grande. Conviene usar este tipo de campo para leer información de una tabla de forma esporádica, no de forma intensiva.

## ¿Cuándo usar el real?

El principal motivo por el que usaremos campos puntero indirecto real, es porque se comporta como un campo puntero a maestro y nos permite lanzar actualizaciones contra el registro apuntado.

Por lo tanto si necesitamos ejecutar actulizaciones siempre debemos usar el puntero indirecto real, en el resto de caso lo normal es usar el virtual, salvo que realicemos muchas lecturas a través de este campo, en cuyo caso es ligeramente más rápido el real que el virtual.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.velneo.com/22/velneo-vdevelop/buenas-practicas-de-programacion/buenas-practicas-de-rendimiento/buenas-practicas-base-de-datos/puntero-indirecto-real-vs-virtual.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.