> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/es/installation/install-store-manager-single-store/installation-sm-connect-to-db.md).

# Conectarse a la base de datos con licencia de la tienda y forzar la instalación de tablas

Este tema describe cómo conectarse a la base de datos con licencia de la tienda y actualizar las tablas de la base de datos de la tienda mediante la función Forzar instalación de tablas.

{% hint style="success" %}
Puede ejecutar Force Install Tables como un ejecutable en **Símbolo del sistema** o **PowerShell**. Esto le permite actualizar o reparar la base de datos de la tienda sin abrir Store Administrator ni Store Manager. Consulte [**Ejecutar Force Install Tables como un ejecutable**](/es/installation/other-procedures/force-install-tables-executable.md) para obtener más información.
{% endhint %}

1. En **Store Administrator**, conéctese a la base de datos de la tienda con licencia. Consulte [**Conectarse a SQL Server y a la base de datos de la tienda**](/es/installation/install-store-manager-single-store/installation-sm-connect-sql-server.md) para obtener más información.
2. En el **Base de datos** panel, haga clic en **Force Install Tables**.

{% hint style="info" %}
A partir de la versión 3.11.14, la función Force Install Tables ya no creará la columna SYNCGUID en las tablas RMH ni en las de aplicaciones de terceros. La función Prepare Database creará la columna SYNCGUID en la tabla RMH, pero ya no la creará en las tablas de aplicaciones de terceros.
{% endhint %}

<div align="left"><img src="https://1556792658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-c471507c9ecc9a583355b6d7f9fd77ed68a4d1f5%2Fstore-administrator-database-menu.png?alt=media" alt=""></div>

3. Haga clic en **Sí** para continuar.

<div align="left"><img src="https://1556792658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-8492fb70c54335fb33b99fd59dee0ff8e39d8599%2Fstore-administrator-force-install-tables.png?alt=media" alt=""></div>

4. Espere mientras **Store Administrator** ejecuta los scripts SQL para crear tablas personalizadas de RMH en la base de datos de la tienda. Esto puede tardar unos minutos.
5. Haga clic en **Aceptar** para cerrar el cuadro de diálogo de confirmación.

<div align="left"><img src="https://1556792658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-c5840d3faa5d1647c37b4e2ce18ddad4c96c8572%2Fstore-administrator-force-install-tables-confirm.png?alt=media" alt=""></div>


---

# 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.rmhpos.com/es/installation/install-store-manager-single-store/installation-sm-connect-to-db.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.
