> For the complete documentation index, see [llms.txt](https://docs.sdv.dev/sdv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sdv.dev/sdv/integration/db.md).
# Connect Your Database
{% hint style="info" %}
❖ **SDV Enterprise Bundle**. This feature is available as part of the **AI Connectors Bundle**, an optional add-on to SDV Enterprise. For more information, please visit the [AI Connectors Bundle](/sdv/explore/sdv-bundles/ai-connectors.md) page.
{% endhint %}
We recommend connecting SDV to your database for the smoothest experience. After integration, SDV is automatically able to create metadata based on the database schema and import data to be used for training an SDV synthesizer.
```python
from sdv.io.database import AlloyDBConnector
# 1. Integration: Create a connector and set your config
connector = AlloyDBConnector()
connector.set_import_config('source_db_config.yaml')
connector.set_export_config('destination_db_config.yaml')
# 2. Usage: Use the API create metadata, import training data, and export synthetic data
metadata = connector.create_metadata(table_names=['users', 'transactions', 'sessions'])
data = connector.import_random_subset(metadata=metadata)
...
connector.export(synthetic_data)
```
## ❖ Browse Databases
Use the AI Connectors feature to directly connect to your database and import your data into SDV. Later you can use the same connector to export synthetic data into a new database.
{% hint style="success" %}
**Request additional databases.** If your database provider is not covered by the list above, please [leave us a request](https://forum.datacebo.com/). If approved our team is able to add a connector for a relational database in a few weeks.
*We prioritize requests made by customers who are using AI Connectors.*
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sdv.dev/sdv/integration/db.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
