> For the complete documentation index, see [llms.txt](https://whiteklay.gitbook.io/virtual-data-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whiteklay.gitbook.io/virtual-data-assistant/key-features/data-sources.md).
# Data Sources
A Datasource is an entity within the Virtual Data Assistant that serves as a container for a collection of metadata. Metadata refers to information about datasets, such as data source location, schema, data types, and other relevant properties. Essentially, a Datasource is like a virtual folder that groups related datasets together.
### Datasource creation uses connectors
Connectors are modules or plugins that establish connections to specific data sources or databases. VDA offers multiple connectors to popular datasources e.g PostgreSQL, MySQL etc. When users select a connector and provide the necessary connection details, it establishes a link to the data source, allowing access to the data within that source.
### Searching Datasets within a Datasource
Once datasets are created and organized within a Datasource, users can perform searches to find specific entities or datasets within that Datasource. This search functionality simplifies data discovery, especially in cases where multiple datasets are stored within the same Datasource.An user can search using specific filters to find appropriate datasets.
### List of Available Connectors (Grouped by Category)
Database Connectors (54) Amazon Athena, Azure SQL, BigQuery, BigTable, BurstIQ, Cassandra, Clickhouse, Cockroach, Couchbase, Custom Database, Databricks, Datalake, Db2, DeltaLake, DomoDatabase, Doris, Dremio, Druid, DynamoDB, Epic, Exasol, Glue, Greenplum, Hive, Iceberg, Impala, Informix, MariaDB, Microsoft Access, Microsoft Fabric, MongoDB, MSSQL, MySQL, Oracle, PinotDB, Postgres, Presto, Redshift, SAS, SQLite, SSAS, Salesforce, SAP ERP, SAP HANA, ServiceNow, SingleStore, Snowflake, StarRocks, Synapse, Teradata, Timescale, Trino, Unity Catalog, Vertica
Dashboard Connectors (20) Custom Dashboard, Domo Dashboard, Grafana, Hex, Lightdash, Looker, Metabase, MicroStrategy, Mode, PowerBI, PowerBI Report Server, QlikCloud, QlikSense, QuickSight, Redash, Sigma, Ssrs, Superset, Tableau, ThoughtSpot
Pipeline Connectors (25) Airbyte, Airflow, Backend, Custom Pipeline, DBT Cloud, Dagster, Data Factory, Databricks Pipeline, Domo Pipeline, Fivetran, Flink, Glue Pipeline, Kafka Connect, Kinesis Firehose, Matillion, Microsoft Fabric Pipeline, Mulesoft, Nifi, OpenLineage, SSIS, Snowplow, Spark, Spline, Stitch, Wherescape
Messaging Connectors (5) Custom Messaging, Kafka, Kinesis, Pulsar, Redpanda
LLM (Large Language Model) Connectors (8) Anthropic, Azure OpenAI, Bedrock, Custom LLM, HuggingFace, Ollama, OpenAI, VertexAI
Storage Connectors (4) Adls, Custom Storage, GCS, S3
Search Connectors (3) Custom Search, Elasticsearch, OpenSearch
Drive Connectors (4) Custom Drive, Google Drive, SFTP, SharePoint
ML Model Connectors (5) Custom ML Model, Mlflow, SageMaker, Sklearn, VertexAI
Metadata Connectors (7) Alation, AlationSink, Amundsen, Atlas, Collibra, MetadataES, OpenMetadata
API & Security Connectors (2) REST API, Ranger (Security)
---
# 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://whiteklay.gitbook.io/virtual-data-assistant/key-features/data-sources.md?ask=&goal=
```
`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.