# Data connection

Marple Insight visualises data by directly connecting to a team's database. This approach ensures that users can analyse measurements without needing to duplicate or migrate data. 

Setting up a connection is simply a matter of providing the necessary credentials and configuration details so that Marple can identify:

* a list of **data sets;**
* within each data set, a **signal list**;
* for a given dataset, signal and time range, **time series data**;
* within time series data, a **segment list.**
  * a segment list is optional, but incredibly powerful in use cases such as motorsport (laps) and flight testing (flight phases) (see [motorsport-package](https://docs.marpledata.com/docs/marple-insight/user-manuals/motorsport-package "mention") and [flight-testing-package](https://docs.marpledata.com/docs/marple-insight/user-manuals/flight-testing-package "mention"))

We have developed a dynamic system that is designed to work with multiple database types, supporting a variety of use cases.

<figure><img src="https://3590686807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEBNWlmdcxXBXd7oyqyR%2Fuploads%2FqHChAnKZ1suEBylGBeEK%2Fconnection-example.webp?alt=media&#x26;token=0d831776-afe7-49b6-8dab-b54392e471db" alt=""><figcaption><p>Example of a connection environment</p></figcaption></figure>