> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/context/memory-stores/add-data/import-from-sql-database.md).
# Import from SQL Database
## Importing from SQL Database
AirOps enables you to connect your Knowledge Base directly to SQL databases, allowing you to import structured data and make it semantically searchable. This powerful integration lets you leverage your existing database information without manual exports.
To import data from an SQL database:
* Click "Add Data" and select "Import from SQL Database" from the dropdown menu
* Select a previously connected database or connect a new one through the settings
* Name your query for future reference
* Write your SQL query, ensuring you include these required columns:
* `id`: A unique identifier for each row
* `content`: The column or concatenated columns you want to make searchable
* Click "Test Connection" to verify your query before importing
* Once verified, import your data to add it to your Knowledge Base
When writing your query, you can use SQL functions like `CONCAT` to combine multiple columns into a single searchable content field, creating richer context for your Knowledge Base.
---
# 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.airops.com/context/memory-stores/add-data/import-from-sql-database.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.
