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

# Supported data sources

Currently, Subsalt directly integrates with:

* MySQL
* Redshift
* Snowflake
* S3 (Parquet)
* Azure storage accounts (Parquet)
* Databricks
* Microsoft SQL Server

If your organization's data source is not listed here, don't worry! Subsalt can connect to any database that supports tabular structured data. Please reach out to the Subsalt team for more information on connecting to your database.

### Connecting to Parquet-based file systems

Subsalt automatically interprets each folder in the target directory as a potential table, with the data being nested in that folder. For example, if you have an S3 bucket called `my-bucket` that is structured like:

* **my-bucket**
  * **my-database**
    * 📁 **customers** <- "customers" will be a table
      * *file\_1.parquet* <- all files in this folder will be combined to make a single "customers" table
      * *file\_2.parquet*
      * *file\_3.parquet*
    * 📁 **product\_imgs** <- since this folder does not have any tabular data it will be ignored
      * *img1.png*
      * *img2.png*
    * 📁 **sales**
      * *file\_1.parquet*
      * *file\_2.parquet*
      * *file\_3.parquet*
      * *file\_4.parquet*

### Connecting to an S3 Bucket

When connecting to an S3 bucket, you will provide a URL; for the example above, the URL would look like this:

**S3 Bucket URL:** `s3://my-bucket/my-database/`

### Connecting to Azure storage

When connecting to an Azure storage account, you will provide a [connection string](https://learn.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string) and a path.

For the example above the configuration would something look like this:

**Connection string:** `BlobEndpoint=https://my-bucket.blob.core.windows.net/;SharedAccessSignature=sv=2022-11-02&ss=b&srt=co&sp=rl&se=2024-10-19T05:27:46Z&st=2024-10-18T21:27:46Z&spr=https&sig=JTrgXgQNvbmPRXumK5rWChznHQRLdaUrTnCjCUmac44%3D`

**Path:** `my-database/`


---

# 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.subsalt.io/configuration/supported-data-sources.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.
