> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-4-2/guides/system-connectivity/databases-time-series-storage.md).

# Databases & Time-Series Storage

These guides describe how to persist shop floor data in relational databases, time-series databases, and search engines, and how to feed query results back into MQTT topics. The following guides are available:

| Guide                                                                                                                       | Connector                                                         | Description                                                     |
| --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------- |
| [Microsoft SQL Server](/2-4-2/guides/system-connectivity/databases-time-series-storage/microsoft-sql-server-integration.md) | [MSSQL](/2-4-2/connectors/enterprise-connectors/mssql.md)         | Write production events and poll query results.                 |
| [PostgreSQL](/2-4-2/guides/system-connectivity/databases-time-series-storage/postgresql-integration.md)                     | [SQL](/2-4-2/connectors/enterprise-connectors/sql.md)             | Write production events and poll query results.                 |
| [MariaDB](/2-4-2/guides/system-connectivity/databases-time-series-storage/mariadb-integration.md)                           | [SQL](/2-4-2/connectors/enterprise-connectors/sql.md)             | Write machine state changes and poll aggregated summaries.      |
| [TimescaleDB](/2-4-2/guides/system-connectivity/databases-time-series-storage/timescaledb-integration.md)                   | [SQL](/2-4-2/connectors/enterprise-connectors/sql.md)             | Write time-series data into hypertables and poll aggregates.    |
| [QuestDB](/2-4-2/guides/system-connectivity/databases-time-series-storage/questdb-integration.md)                           | [HTTP/REST](/2-4-2/connectors/enterprise-connectors/http-rest.md) | Stream time-series data using InfluxDB Line Protocol over HTTP. |
| [ClickHouse](/2-4-2/guides/system-connectivity/databases-time-series-storage/clickhouse-integration.md)                     | [HTTP/REST](/2-4-2/connectors/enterprise-connectors/http-rest.md) | Stream data into MergeTree tables over the HTTP interface.      |
| [InfluxDB](/2-4-2/guides/system-connectivity/databases-time-series-storage/influxdb-service-integration.md)                 | [InfluxDB](/2-4-2/connectors/enterprise-connectors/influxdb.md)   | Deploy InfluxDB as a service and store OPC UA data.             |
| [Elasticsearch](/2-4-2/guides/system-connectivity/databases-time-series-storage/elasticsearch-integration.md)               | [MQTT](/2-4-2/connectors/enterprise-connectors/mqtt.md)           | Ship data to Elasticsearch using the Filebeat MQTT input.       |


---

# 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 dynamically by asking a question.

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

```
GET https://docs.cybus.io/2-4-2/guides/system-connectivity/databases-time-series-storage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.