# Double-onboard a data source

To scan your data for quality, Soda must connect to a data source using connection configurations (host, port, login credentials, etc.) that you either define in Soda Cloud during onboarding using a Soda Runner, or in a configuration YAML file you reference during programmatic or CLI scans using Soda Library. Soda recognizes each data source you onboard as an independent resource in Soda Cloud, where it displays all scan results and failed row samples for all data sources regardless of onboarding method.

However, data sources you connect via a Soda Runner using the guided workflow in Soda Cloud support several features which data sources you connect via Soda Library do not, including:

* [no-code checks](/soda-documentation/soda-v3/soda-cl-overview.md#define-sodacl-checks)
* [Discussions](/soda-documentation/soda-v3/use-case-guides/quick-start-end-user.md#begin-a-discussion-and-propose-checks)
* [scan scheduling](/soda-documentation/soda-v3/run-a-scan.md#scan-for-data-quality)
* [anomaly dashboards](/soda-documentation/soda-v3/collaborate/anomaly-dashboard.md) **Available in 2025**

If you have onboarded a data source via Soda Library but you wish to take advantage of the features available to Soda Runner-onboarded data sources, you can double-onboard an existing data source.

> See also: [Soda overview](/soda-documentation/soda-v3/learning-resources/product-overview.md)
>
> See also: [Choose a flavor of Soda](/soda-documentation/soda-v3/quick-start-sip/setup-guide.md)
>
> See also: [Add a new data source](/soda-documentation/soda-v3/quick-start-sip/managed-agent.md) in Soda Cloud

## Prerequisites

* You [installed Soda Library](/soda-documentation/soda-v3/quick-start-sip/install.md), you have configured it to connect to your data source, and you have run at least one [scan](/soda-documentation/soda-v3/run-a-scan.md#scan-for-data-quality) programmatically or via the Soda Library CLI.
* You have deployed a [self-hosted Soda Runner](/soda-documentation/soda-v3/quick-start-sip/deploy.md) Helm chart in a Kubernetes cluster in your cloud services environment\
  OR\
  Someone with Soda Admin privileges in your organization’s Soda Cloud account has navigated to **your avatar** > **Organization Settings** check the box to **Enable Soda-hosted Runner**; see [Set up a Soda-hosted runner](/soda-documentation/soda-v3/quick-start-sip/managed-agent.md).
* You have access to the connection configurations (host, port, login credentials, etc.) for your data source.
* Your data source is compatible with a Soda Runner; refer to tables below.

#### Self-hosted runner

| <p>Amazon Athena<br>Amazon Redshift<br>Azure Synapse<br>ClickHouse<br>Databricks SQL<br>Denodo<br>Dremio<br>DuckDB<br>GCP BigQuery<br>Google CloudSQL</p> | <p>IBM DB2<br>MotherDuck<br>MS SQL Server<sup>1</sup><br>MySQL<br>OracleDB<br>PostgreSQL<br>Presto<br>Snowflake<br>Trino<br>Vertica</p> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |

<sup>1</sup> MS SQL Server with Windows Authentication does not work with Soda Runner out-of-the-box.

#### Soda-hosted runner

| <p>BigQuery<br>Databricks SQL<br>MS SQL Server<br>MySQL</p> | <p>PostgreSQL<br>Redshift<br>Snowflake<br></p> |
| ----------------------------------------------------------- | ---------------------------------------------- |

## Onboard an existing data source

1. Log in to Soda Cloud, then navigate to **your avatar** > **Data Sources**.
2. From the list of data sources connected to your Soda Cloud account, click to select and open the one you onboarded via Soda Library and now wish to double-onboard via a Soda Runner.
3. Follow the guided workflow to onboard the existing data source via a Soda Runner, starting by using the dropdown to select the **Default Scan Runner** you wish to use to connect to the data source.
4. Complete the [guided steps](/soda-documentation/soda-v3/quick-start-sip/managed-agent.md#add-a-new-data-source) to:

* define a schedule for your default scan definition
* provide connection configuration details for the data source such as name, schema, and login credentials, and test the connection to the data source
* profile the datasets in the data source to gather basic metadata about the contents of each
* identify the datasets to which you wish to apply automated monitoring for anomalies and schema changes
* assign ownership roles for the data source and its datasets

5. **Save** your changes, then navigate to the **Datasets** page and select a dataset in the data source you just double-onboarded.
6. (Optional) If you wish, and if you have [requested preview access](https://go.soda.io/join-observability-preview) for the feature, you can follow the instructions to [activate the anomaly dashboard](/soda-documentation/soda-v3/collaborate/anomaly-dashboard.md) for the dataset.
7. (Optional) Click **Add Check** and begin adding [no-code checks](/soda-documentation/soda-v3/soda-cl-overview.md#define-sodacl-checks) to the dataset.

***Known issue***: Double-onboarding a data source renders Soda Library API keys invalid. After double-onboarding a data source, if you run a programmatic or CLI scan of that data source using Soda Library, an error appears to indicate that the API keys are invalid. As a workaround, [generate new API keys](/soda-documentation/soda-v3/use-case-guides/api-keys.md) in Soda Cloud, then, in your configuration YAML, replace the old API key values with the newly-generated ones.

## Go further

* Learn more about [automating anomaly detection](/soda-documentation/soda-v3/collaborate/anomaly-dashboard.md) for observability.

> Need help? Join the [Soda community on Slack](https://community.soda.io/slack).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.soda.io/soda-documentation/soda-v3/use-case-guides/double-onboard-datasource.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.