> For the complete documentation index, see [llms.txt](https://docs.zenlytic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenlytic.com/data-sources/teradata_setup.md).

# Teradata Setup

Connect Teradata to Zenlytic and verify access to your database.

To connect Zenlytic to Teradata, gather the connection details from your database administrator.

## Gather connection information

* **Host**: Your Teradata hostname or IP address
* **Database**: The database to connect to
* **Username and password**: Credentials for a user with access to the data you want to query
* **Port (optional)**: Leave blank to use the default, 1025
* **Schema (optional)**: Leave blank to use the user's default schema

## Add the data source

1. In Zenlytic, go to **Settings > Data Sources**.
2. Select **Add Data Source**, then **Teradata**.
3. Enter the connection details.
4. Test the connection. A successful test confirms that Zenlytic can reach and authenticate to Teradata.
5. Save the data source.

## Troubleshooting

If the test fails, check the host and port, confirm the credentials and database name, and verify that the user can access the tables you intend to use. If your network restricts incoming connections, allow the addresses for your Zenlytic deployment listed in [IP Whitelisting](https://docs.zenlytic.com/authentication-and-security/ip_whitelisting.md), then test again.


---

# 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.zenlytic.com/data-sources/teradata_setup.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.
