Skip to content

Adding a New Datastore Using an Existing Connection

This guide walks you through creating a new source datastore on the Add Datastore page by reusing credentials from a connection that already exists, saving time and ensuring consistency. To set up a connection from scratch instead, see Add Source Datastore.

Connection Properties

When reusing an existing connection, the Connection Properties come collapsed and read-only: you only configure the extraction fields and the Datastore Properties below them. To change the credentials themselves, edit the connection through the Manage Connections page.

Start a new connection from this one

To use a saved connection as a starting point for a brand-new connection instead, click the Duplicate as a new connection button on the selected connection. The form switches to New Connection mode with the connection's settings already filled in for you to adjust.

Field reference

Pick the tab that matches the connector family of the connection you are reusing.

For relational databases and warehouses, the Datastores Extraction group asks where the datastore points inside the connected database:

jdbc-fields-reference

REF. REQUIRED DESCRIPTION
1 Database: select or type the database the datastore covers.
2 Schema: select or type one or more schemas within the database.

Multiple schemas

On connectors that support it, selecting more than one schema creates one source datastore per schema, named from the Name Template. See Multi-Schema Source Datastore Creation for details.

Below the extraction fields come the Datastore Properties:

jdbc-fields-reference-2

REF. REQUIRED DESCRIPTION
1 Name Template: defines the naming pattern for each source datastore being created, combining the template with the schema name (e.g., dev_{{schema}}_sales). Left empty, the datastore is named from the connection name and the schema.
2 Group: organizes your datastores under a shared group in the navigation tree. Turn on Add New Group to create a new group instead of selecting an existing one.
3 Teams: one or more teams to associate with this source datastore.
4 Initiate Sync: automatically sync the datastore to detect containers and fields right after creation.

For cloud object storage, the Datastores Extraction group asks for the path the datastore reads from:

dfs-fields-reference

REF. REQUIRED DESCRIPTION
1 Root Path: the folder inside the storage location that the datastore reads from. Use / to read from the root.

Multiple folders

Selecting more than one folder creates one source datastore per folder, named from the Name Template.

Below the extraction field come the Datastore Properties:

dfs-fields-reference-2

REF. REQUIRED DESCRIPTION
1 Name Template: defines the naming pattern for each source datastore being created, combining the template with the folder name (e.g., rides_{{path}}). Left empty, the datastore is named from the connection name and the path.
2 Group: organizes your datastores under a shared group in the navigation tree. Turn on Add New Group to create a new group instead of selecting an existing one.
3 Teams: one or more teams to associate with this source datastore.
4 Initiate Sync: automatically sync the datastore to detect containers and fields right after creation.

Steps

Use this flow when the saved connection points at a relational database or warehouse, such as PostgreSQL, Snowflake, or SQL Server.

Step 1: Click Add Source Datastore at the top-right of the Source Datastores page.

step-1-add-source-datastore

Step 2: Select Existing Connection next to the search field.

step-2-existing-connection

Step 3: Select the connection you want to reuse from the grid. Each card shows the connection name and its connector. Use the search field to filter by name.

step-3-select-connection-jdbc

Step 4: Fill in the Datastores Extraction fields and the Datastore Properties described in the Field reference. The Connection Properties come from the selected connection and are read-only. Then click Test connection.

step-4-test-connection-jdbc

Step 5: A success message confirms that the connection has been verified. Click Finish to create the datastore.

step-5-finish-jdbc

Info

The Finish and Next buttons stay disabled until the connection test passes on the current values. If the test fails, check the connector's troubleshooting page.

Tip

To link an enrichment datastore so Qualytics can store anomalies and metadata from the first operation, click Next instead of Finish. See Link Enrichment on Datastore Creation.

Step 6: A success dialog confirms that your datastore has been added. Click Go to your datastore to open its page.

step-6-success-dialog-jdbc

Use this flow when the saved connection points at cloud object storage, such as Amazon S3, Azure Data Lake Storage, or Google Cloud Storage.

Step 1: Click Add Source Datastore at the top-right of the Source Datastores page.

step-1-add-source-datastore

Step 2: Select Existing Connection next to the search field.

step-2-existing-connection

Step 3: Select the connection you want to reuse from the grid. Each card shows the connection name and its connector. Use the search field to filter by name.

step-3-select-connection-dfs

Step 4: Fill in the Datastores Extraction field and the Datastore Properties described in the Field reference. The Connection Properties come from the selected connection and are read-only. Then click Test connection.

step-4-test-connection-dfs

Step 5: A success message confirms that the connection has been verified. Click Finish to create the datastore.

step-5-finish-dfs

Info

The Finish and Next buttons stay disabled until the connection test passes on the current values. If the test fails, check the connector's troubleshooting page.

Tip

To link an enrichment datastore so Qualytics can store anomalies and metadata from the first operation, click Next instead of Finish. See Link Enrichment on Datastore Creation.

Step 6: A success dialog confirms that your datastore has been added. Click Go to your datastore to open its page.

step-6-success-dialog-dfs