> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.206/help-center-index/faqs/installer-faqs/oim-and-database-on-same-server.md).

# Is it mandatory for the database to be installed on the same server on which the application is inst

### Description

<code class="expression">space.vars.SITENAME</code> supports 4 types of databases: HSQL, MYSQL, MSSQL, ORACLE, PostgreSQL. Among these, HSQL is the in-built database provided with <code class="expression">space.vars.SITENAME</code>.\
However, you can use one of the other external databases like MYSQL, MSSQL, ORACLE, or PostgreSQL. So in such case, is it necessary to install the <code class="expression">space.vars.SITENAME</code> on the same machine where the database is hosted?

### Solution

It is not mandatory to have the database on the same machine where <code class="expression">space.vars.SITENAME</code> is installed. They can reside on different machines as long as [database pre-requisites](/v7.206/getting-started/prerequisites.md#database-prerequisites) and [hardware pre-requisites](/v7.206/getting-started/prerequisites.md#hardware-prerequisites) are fulfilled for them. The machine on which <code class="expression">space.vars.SITENAME</code> is installed should be able to access the machine on which the database has been placed.\
It is better to have strong connectivity to the database machine to ensure smooth performance of <code class="expression">space.vars.SITENAME</code>.

> **Note**: Installation of <code class="expression">space.vars.SITENAME</code> with HSQL database will automatically create the database on the same machine, as HSQL is the default embedded database of <code class="expression">space.vars.SITENAME</code>.


---

# 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.opshub.com/v7.206/help-center-index/faqs/installer-faqs/oim-and-database-on-same-server.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.