> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/getting-started/setup/repository-database.md).

# Repository database

**Database** is the second step of the wizard. WriteBackExtreme needs a database of its own to store its internal data: schemas, users, groups, audits and settings. This is **not** the database you write back to from Tableau or Power BI.

Choose the engine under **Driver** and fill in the connection details. The fields are the same for every engine:

| Field                 | Notes                                                      |
| --------------------- | ---------------------------------------------------------- |
| **Database host**     | Defaults to `127.0.0.1`.                                   |
| **Database port**     | Prefilled with the default port for the engine you picked. |
| **Database name**     | The database has to exist already, except on SQLite.       |
| **Database username** | Required.                                                  |
| **Database password** | Required.                                                  |
| **Default schema**    | PostgreSQL only. Defaults to `public`.                     |

Press **Next** to test the connection and save it. **Connection success!** means WriteBackExtreme could reach the database with the details you gave.

{% hint style="danger" %}
Passwords **cannot** contain a `$` sign. The wizard rejects them with **Dollar sign ($) is not allowed.**
{% endhint %}

The repository database engine cannot be changed after setup. If you need a different engine later, do a fresh installation.

Pick your engine for the details that differ:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>SQL Server</td><td><a href="https://docs.infotopics.com/getting-started/setup/repository-database/sql-server.md">SQL server</a></td></tr><tr><td>MySQL</td><td><a href="https://docs.infotopics.com/getting-started/setup/repository-database/mysql.md">MySQL</a></td></tr><tr><td>PostgreSQL</td><td><a href="https://docs.infotopics.com/getting-started/setup/repository-database/postgresql.md">PostgreSQL</a></td></tr><tr><td>SQLite</td><td><a href="https://docs.infotopics.com/getting-started/setup/repository-database/sqlite.md">SQLite</a></td></tr></tbody></table>

For WriteBackExtreme Trial and Docker we use **SQLite** as our repository database. Checkout our Docker installation guide or request a trial via [our website](https://appsfortableau.infotopics.com/writebackextreme-trial/).

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th align="right"></th><th align="right"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="right"><strong>Previous</strong></td><td align="right">License</td><td><a href="https://docs.infotopics.com/getting-started/setup/repository-database.md">Repository database</a></td></tr></tbody></table>


---

# 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.infotopics.com/getting-started/setup/repository-database.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.
