> 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/v5.0/installation-guide/getting-started/containerization/odbc-connections.md).

# ODBC connections

ODBC Databases with unique setups: This document describes databases with distinct communication methods:

* Snowflake ODBC
* Databricks

ODBC-based drivers are exposed and can be used via the driver name. 

* Snowflake ODBC: `SnowflakeDSIIDriver`
* Databricks: `DatabricksDriver`

### Using `odbc.ini` and or `odbcinst.ini`

If it's necessary to use an `odbc.ini` file for defining connections, create a `VOLUME` pointed to `/etc/odbc.ini` or populate the `odbc.ini` file with content beforehand. For driver modifications, use `/etc/odbcinst.ini` as needed.

### Snowflake ODBC

We recommend to use the "manual DSN" setup in WriteBackExtreme when using the containerized version.

Example DSN string:

```
driver=SnowflakeDSIIDriver;....
```

### Databricks

To connect to Databricks, a "manual DSN" isn't available yet. Use the following workaround instead. The table below lists all required DSN attributes.

<table><thead><tr><th width="161">Key</th><th width="102" data-type="checkbox">Required</th><th width="118" data-type="checkbox">Fixed value</th><th>Value/Example</th></tr></thead><tbody><tr><td>driver</td><td>true</td><td>true</td><td>DatabricksDriver</td></tr><tr><td>httpPath</td><td>true</td><td>false</td><td>e.g. /sql/1.0/warehouses/123456789</td></tr><tr><td>thriftTransport</td><td>true</td><td>true</td><td>2</td></tr><tr><td>AuthMech</td><td>true</td><td>true</td><td>3</td></tr><tr><td>Host</td><td>true</td><td>false</td><td>e.g. abc-123456789.azuredatabricks.net</td></tr><tr><td>Port</td><td>true</td><td>true</td><td>443</td></tr><tr><td>Ssl</td><td>true</td><td>true</td><td>1</td></tr><tr><td>transportMode</td><td>true</td><td>true</td><td>http</td></tr></tbody></table>

The attributes specified will generate a DSN string as follows:

<pre><code><strong>driver=DatabricksDriver;HttpPath={htthPath};thriftTransport=2;AuthMech=3;Host={host};Port=443;ssl=1;transportMode=http
</strong></code></pre>

<figure><img src="https://content.gitbook.com/content/MzOBMgQCQmnHEY9CGpbe/blobs/u0t70HuC0WMgOJLW2jv5/image.png" alt=""><figcaption></figcaption></figure>


---

# 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/v5.0/installation-guide/getting-started/containerization/odbc-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.