> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/database/mariadb_mysql.md).

# MariaDB / MySQL

## **Why syncing my MariaDB / MySQL to** [**Whaly**](https://whaly.io)**?**

Syncing your MariaDB / MySQL can be useful for various cases

* Share your product usage with your support and customer success team
* Combine MariaDB / MySQL data with your CRM data to detect churn or upsells
* ....

## Requirements

1. Allow connections from Whaly to your MariaDB / MySQL database by [whitelisting Whaly IPs](/connectors/whitelisting-whaly-connectors-ips.md)

## Support

| Table type | Supported            |
| ---------- | -------------------- |
| TABLE      | :white\_check\_mark: |
| VIEW       | :red\_circle:        |

## Configuring the source

The MariaDB / MySQL connector will need the following information:

* **Host**: This should be an IP address or an URL pointing to your MariaDB / MySQL server
* **Port**: This should be the Port of your MariaDB / MySQL, Default to `3306`.
* **User**: This should be the username of a read only MariaDB / MySQL user with read access.
* **Password**: The password associated with the user


---

# 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.whaly.io/connectors/source-catalog/database/mariadb_mysql.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.