> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi.md).

# Use a Pentaho Repository in PDI

The PDI client (also known as Spoon) offers several different types of file storage. A Pentaho Repository stores transformations, jobs, and schedules in a central environment through the Pentaho Server. It is recommended for enterprise deployments and fully supported features.

If your team needs a collaborative ETL (Extract, Transform, and Load) environment, we recommend using one or more than one Pentaho Repository. In addition to storing and managing your jobs and transformations, A Pentaho Repository provides full revision history for you to track changes, compare revisions, and revert to previous versions when necessary. These features, along with enterprise security and content locking, make using a Pentaho Repository an ideal platform for collaboration.

You can use the following information in the **Administer Pentaho Data Integration and Analytics** document to help to extend your knowledge of a Pentaho Repository beyond basic setup and use:

* [Create a connection in the PDI client](/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/create-a-connection-in-the-pdi-client.md)
* [Connect to a Pentaho Repository](/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/connect-to-a-pentaho-repository.md)
* [Manage repositories in the PDI client](/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/manage-repositories-in-the-pdi-client.md)
* [Unsupported repositories](/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/unsupported-repositories.md)
* [Use the Repository Explorer](/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi/use-the-repository-explorer.md)

## Advanced topics

To extend your knowledge of a Pentaho Repository beyond basic setup and use, see the following topics in the [Administer Pentaho Data Integration and Analytics](/pdia-admin/10.2-admin/book-abstract-for-administer-pdia.md) guide: 

* [**Import and export PDI content**](/pdia-admin/10.2-admin/manage-the-pentaho-system/manage-the-pentaho-repository/import-and-export-pdi-content.md)

  Repository content can also be imported and exported through either the PDI client or a command line interface.
* [**Purge transformations, jobs, and shared objects from the Pentaho Repository**](/pdia-admin/10.2-admin/manage-the-pentaho-system/manage-the-pentaho-repository/purge-transformations-jobs-and-shared-objects-from-the-pentaho-repository.md)

  If the Pentaho Repository becomes too large for effective system performance, consider purging some of the data.
* [**Backup and restore a Pentaho Repository**](/pdia-admin/10.2-admin/manage-the-pentaho-system/manage-the-pentaho-repository/backup-and-restore-pentaho-repositories.md)

  Perform routine backups to minimize potential data loss through machine failure, theft, disaster, or accidental change.


---

# 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.pentaho.com/pdia-data-integration/9.3-data-integration/use-a-pentaho-repository-in-pdi.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.