# Connection configuration
Wire up your connection by following the following steps (detailed explanation below):
1. Choose database type
2. Connect to your database
3. Define datasets
4. Write the required queries
To establish a connection, navigate to **Settings → Connection**.
## Step 1: Choose database type
In the **Overview** tab, you can change the type of database you want to connect to.
You can also export the current connection setup (including all the queries), or import connection settings from a JSON.
To get some guidance, you can start by uploading these test queries (written for Postgres databases):
{% file src="/files/uMRum57Ljb0XhSVHXc1G" %}
Connection overview
Read more:
{% content-ref url="/pages/27I0fxw8rW4lZlpYTyXW" %}
[Supported Databases](/docs/marple-insight/setup-and-configuration/data-connection/supported-databases.md)
{% endcontent-ref %}
## Step 2: Connect to your database
Before configuring a connection, ensure that you have configured all necessary credentials. The required values differ between database types.
After selecting the database type in the **Overview** tab, move to **Connection** to fill in the credentials.
Use "Test Connection" to make sure everything works. It should give a green checkmark (✅)
Connection credentials
## Step 3: Define datasets
Marple Insight has a "dataset-oriented" approach.\
Start by defining 1 or more dataset metadata keys that define a dataset uniquely. Each dataset will shown in the library as a separate entry that can be analysed.
A dataset can be for example one flight test, race data for 1 car, ...
In the **Metadata** tab, you can define all dataset metadata that is shown in Marpe.
Mark the dataset identifiers as "filter". Those values can later be used in the queries, e.g. as *dataset.dataset\_id*.
## Step 4: Queries
Next, within the Marple Insight application, you'll need to define a set of queries that allow Marple to interpret and retrieve your data.
There are **required queries**—such as those for datasets, signal lists, and time-series data—as well as **optional queries**, like segment-based queries.
Make sure to wire up all required queries to enable Marple Insight on your data.
{% content-ref url="/pages/euN2F0K10q9TWLyBBgJy" %}
[Required Queries](/docs/marple-insight/setup-and-configuration/data-connection/connection-configuration/required-queries.md)
{% endcontent-ref %}
{% content-ref url="/pages/eoWSYKXGgjR9aahD9zhz" %}
[Optional Queries](/docs/marple-insight/setup-and-configuration/data-connection/connection-configuration/optional-queries.md)
{% endcontent-ref %}
These queries are written using the Jinja templating language, which makes them dynamic and adaptable to different database structures.
{% content-ref url="/pages/B4n5EcAPkbCV7AXG7fhA" %}
[Templating](/docs/marple-insight/setup-and-configuration/data-connection/connection-configuration/templating.md)
{% endcontent-ref %}
## Need help?
Our team has a lot of expertise in setting up Marple Insight for customers. Get in touch if you have any questions:
{% content-ref url="/pages/8SkXB1SRqj5MoqRQzPMa" %}
[Feedback](/docs/marple-insight/welcome/feedback.md)
{% endcontent-ref %}
---
# 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.marpledata.com/docs/marple-insight/setup-and-configuration/data-connection/connection-configuration.md?ask=
```
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.