> 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/writebackextreme/features/database-connections.md).

# Database connections

Connections hold information about the connections to your databases. You only have to do this once for every database connection you would like to use for a WriteBack scenario. The username and password of a connection are stored safely and encrypted in our back-end.

A schema is connected to one of the available connections. You can have multiple schemas connected to one single connection. You can simply state that a connection is the authorized path to a database server and one database to store or edit write back information via the schemas within the available modules.

Access to connections is restricted to admins or to users with the connection manager role.

### ODBC

Snowflake, Databricks, and Teradata use ODBC for connectivity. To use these databases with an on-premise installation, you must first install the appropriate ODBC drivers and configure them using ODBC Manager on Windows or /etc/odbc.ini & /etc/odbcinst.ini on Linux.

SAP HANA uses ODBC for connectivity in WriteBackExtreme versions 5.5 through 6.1.3. Starting with version 6.2.0, SAP HANA uses JDBC instead, and ODBC is no longer supported for SAP HANA.

{% hint style="info" %}
Databases with a special ODBC setup are shown below
{% endhint %}

{% content-ref url="/pages/3GX5KxYrqjkReqYe4tGc" %}
[DataBricks](/writebackextreme/features/database-connections/databricks.md)
{% endcontent-ref %}

{% content-ref url="/pages/vkqklqICzwvbuvNGB7xK" %}
[Snowflake](/writebackextreme/features/database-connections/snowflake.md)
{% endcontent-ref %}


---

# 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/writebackextreme/features/database-connections.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.