> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt > Use this file to discover all available pages before exploring further. # Database Connectors > Discover Collate's database connectors to seamlessly integrate MySQL, PostgreSQL, Snowflake, and 50+ data sources for metadata management. # Database Services This is the supported list of connectors for Database Services:

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

BETA

PROD

If you have a request for a new connector, don't hesitate to reach out in [Slack](https://slack.open-metadata.org/) or open a [feature request](https://github.com/open-metadata/OpenMetadata/issues/new/choose) in our GitHub repo. ## Configure Metadata Agent and Schedule Ingestion The **Metadata Agent** extracts schemas, tables, columns, and other structural metadata from your source and keeps your Collate catalog in sync. It powers discovery, lineage, and governance across your data assets. When you click **Create & Deploy**, Collate automatically deploys a Metadata Agent for this service and triggers the first ingestion run. View its status and run history from the **Agents** tab on the service detail page. To configure the additional Metadata Agent and schedule ingestion, follow these steps: 1. In the left navigation, click **Connections** and select your service. 2. Click the **Agents** tab. 3. Click **Add Agent** and select **Metadata** from the dropdown. Add Metadata Agent

For some services, the dropdown is not available and clicking **Add Agent** takes you directly to the agent configuration page. 4. On the **Configure Ingestion** page, do the following and click **Next**. * **Name this Ingestion**: Enter a unique recognizable name for this ingestion pipeline.

* **Agent Setup**: Configure core parameters for metadata extraction. The following fields are available: | Field | Default | Description | | ------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------ | | Default Owner | — | Owner applied to all entities when no specific level owner is configured. Accepts a user or team name/email. | | Service Owner | — | Owner assigned to the service entity. | | Database Owner | — | Owner assigned to all ingested databases. Accepts a single owner or a per-database name mapping. | | Database Schema Owner | — | Owner assigned to all ingested schemas. Accepts a single owner or a per-schema name mapping. | | Table Owner | — | Owner assigned to all ingested tables. Accepts a single owner or a per-table name mapping. | | Enable Inheritance | On | When on, child entities inherit the owner from their parent when they have no owner configured. | | Query Log Duration | 1 | Number of days to look back in query logs when processing stored procedure results. | | Query Parsing Timeout Limit | 300 | Timeout in seconds for parsing a single query. | | Number of Threads | 1 | Number of threads to use for parallel table ingestion. | | Incremental Extraction | Off | When enabled, subsequent runs only extract entities changed since the last successful run. | | Successful Pipeline Run Lookback Days | 7 | Number of days to search back for a prior successful run to use as a baseline for incremental extraction. | | Safety Margin Days | 1 | Additional days added to the baseline timestamp as a buffer for incremental extraction. | | JSON Schema Sample Size | 10 | Number of rows sampled to infer JSON column schema. Only applies when Extract JSON Schema is enabled in Advanced Config. | Agent Setup

* **Filter Patterns**: Apply include or exclude rules to scope which databases, schemas, tables, and stored procedures this agent ingests. For more information about various filter options, see **Step 5: Configure Ingestion Options**.

* **Scope & Behaviour**: Control how the agent handles metadata during ingestion. Toggle each option on or off based on your needs: | Toggle | Default | Description | | ------------------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Include Tables | On | Ingest table metadata from the source. Turn off to skip tables entirely. | | Include Tags | On | Ingest tags from the source. | | Include Stored Procedures | On | Ingest stored procedure metadata. | | Include DDL Statements | Off | Ingest DDL statements alongside table metadata. | | Include Owners | Off | Assign owners to ingested entities when the source owner's email matches a user in Collate. Does not overwrite an existing owner. | | Include Custom Properties | Off | Ingest connector-specific custom properties onto entities. | | Mark Deleted Tables | On | Soft-delete tables in Collate when they are removed from the source. Applies only within the currently ingested schema. | | Mark Deleted Stored Procedures | On | Soft-delete stored procedures in Collate when they are removed from the source. | | Mark Deleted Schemas | Off | Soft-delete schemas and all their child assets when removed from the source. | | Mark Deleted Databases | Off | Soft-delete databases and all their child assets when removed from the source. | | Override Metadata | Off | When on, source values overwrite existing descriptions, tags, owners, and display names in Collate. When off, Collate only updates fields that have no existing value. | | Enable Debug Log | Off | Sets the ingestion log level to DEBUG. Useful for troubleshooting. | **Note**: Available toggles vary by connector. Stored procedure options only appear for connectors that support stored procedures. Scope & Behaviour

* **Advanced Config**: Optional connector-specific settings such as Include Views and Extract JSON Schema.

5. On the **Schedule Interval** page, set when the agent runs: * **Schedule**: Choose a preset interval (Hourly, Daily, Weekly, Monthly) or enter a custom cron expression. * **On-Demand**: No automatic schedule; trigger the agent manually when needed.

6. Click **Add** to deploy the agent.