> 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/databricks.md).

# DataBricks

WriteBackExtreme can connect to Databricks by using the Databricks ODBC Driver.

For Windows installations, we recommend creating a 64-bit System DSN on the WriteBackExtreme server. This is required when WriteBackExtreme runs as a Windows service, because User DSNs and user-only encrypted passwords may not be accessible to the service account.

For Linux installations, configure the Databricks ODBC Driver and connection settings directly on the server.

Before continuing, make sure you have the following Databricks connection details available:

* Server hostname
* HTTP Path
* Port, usually `443`
* Catalog and database/schema, if applicable
* Authentication details, for example username `token` and a Databricks personal access token

### Select OS

{% content-ref url="/pages/uvOPkFkd8SyvcYW4YhD2" %}
[Windows old](/writebackextreme/features/database-connections/databricks/windows-old.md)
{% endcontent-ref %}

{% content-ref url="/pages/TiTcUIDWlViihvxHi9P9" %}
[Linux](/writebackextreme/features/database-connections/databricks/linux.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/databricks.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.