> For the complete documentation index, see [llms.txt](https://docs.peoplelogic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peoplelogic.dev/guides/getting-started-with-the-talent-agent-sdk/advanced/using-a-remote-database.md).

# Using a remote database

When using the CLI with the Agent SDK, it comes pre-configured for using a local database powered by H2.  In all other use cases, you'll need to configure a JDBC connection.  Once defined, the SDK will take care of building the database and keeping it up to date for you.

To configure the database, you just need to adding the following to your `application.properties` where the items in ${} are environment variables that you should define.

```properties
agent.datasource.type=${DATABASE_TYPE:postgresql}
spring.datasource.url=jdbc:${agent.datasource.type}://${DATABASE_HOST:}:${DATABASE_PORT:5432}/${DATABASE_NAME:people_team_agents}
spring.datasource.username=${DATABASE_USERNAME:}
spring.datasource.password=${DATABASE_PASSWORD:}
```

The SDK includes the PostgreSQL JDBC drivers and the H2 drivers by default.  If you would like to use another database you should include it's JDBC driver in your `build.xml`.


---

# 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://docs.peoplelogic.dev/guides/getting-started-with-the-talent-agent-sdk/advanced/using-a-remote-database.md?ask=<question>&goal=<endgoal>
```

`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.