> 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/store-manager/configure-pos-and-store-manager/offline-database/administrator-about-offline-db.md).

# About the offline database

You can configure an offline database for each POS register that allows cashiers and salespeople to continue processing sales transactions if POS loses its connection to the store database.

The offline database cannot be connected to the same SQL Server instance as the store database. It is recommended that you install Microsoft SQL Server Express on the same computer as POS, create a unique SQL Server instance for the offline database, and then connect the offline database to that SQL Server instance. An empty store database, **rmhdb.bck**, is shipped with RMH that you can use for the offline database. It is usually available under **C:\Program Files (x86)\Retail Hero\RMH Store Manager\DBFiles**.

When POS loses its connection to the store database, a warning message displays in POS and the cashier or salesperson is offered two options: try to reconnect to the store database or close the POS app. If attempts to reconnect to the store database fail, the cashier or salesperson should close and restart the POS app. When POS restarts, it connects to the offline database and a message displays to indicate that POS is operating in offline mode.

{% hint style="warning" %}
In offline mode, cashiers or salespeople can continue to process sales transactions. However, it is not possible to process more complicated transactions such as quotes, layaways, or work orders. In addition, integrated payment processing may be impacted. Stores should have a failover solution in place for payment processing to ensure they are able to continue processing payments if POS loses its connection to SQL Server and the store database.
{% 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 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://docs.rmhpos.com/store-manager/configure-pos-and-store-manager/offline-database/administrator-about-offline-db.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.