Skip to content

Supported Connectors for Enrichment Datastores

Any datastore can link to an enrichment datastore as its destination, but only connectors that let Qualytics write can host one. Qualytics creates and updates outputs that hold scan results, source records, remediation snapshots, materialized copies, and exported metadata. The connector lists below show which connectors are supported.

Available Datastore Connectors

For the full list of connectors, including those that can only be a source, see the Available Datastore Connectors page.

What gets written

For the outputs Qualytics writes into a destination and their columns, see Enrichment Outputs and Export Outputs.

JDBC Connectors

A JDBC enrichment datastore holds the written outputs as tables in the relational database itself. Out of 20 JDBC connectors, 11 can host one.

No. Connector Logo Enrichment Datastore
1. Athena Athena
2. BigQuery BigQuery
3. Databricks Databricks
4. DB2 DB2
5. Dremio Dremio
6. Fabric Analytics Fabric
7. Hive Hive
8. MariaDB MariaDB
9. Microsoft SQL Server SQL Server
10. MySQL MySQL
11. Oracle Oracle
12. PostgreSQL PostgreSQL
13. Presto Presto
14. Redshift Redshift
15. SAP HANA SAP HANA
16. Snowflake Snowflake
17. Synapse Synapse
18. Teradata Teradata
19. TimescaleDB Timescale
20. Trino Trino

Native Connectors

Hive Native is read-only and cannot be used as an enrichment datastore. Create one on another connector and link it as the destination.

Databricks Native

Databricks-based deployments also provide a deployment-specific Databricks Native connector that can receive enrichment data. It is not available in every deployment, so it is not listed below.

No. Connector Logo Enrichment Datastore
1. Hive Native Hive Native

DFS Connectors

A DFS enrichment datastore holds the written outputs in Delta format in cloud object storage. All 3 DFS connectors can host one.

No. Connector Logo Enrichment Datastore
1. Amazon S3 S3
2. Azure Datalake Storage (ABFS) ABFS
3. Google Cloud Storage (GCS) GCS