> 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/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-a-pentaho-administrator/define-data-connections/modify-connections/modify-connections-from-pdi.md).

# Modify connections from PDI

Access other database-related connection tasks in PDI by right-clicking on the connection name in the **View** tab of the **Explorer** pane, as shown below:

![Other database-related tasks](https://3280820413-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy1poGLvhSUVhf3TOysqu%2Fuploads%2Fgit-blob-93d13a3d14ac7190c31e9b8981f171eed36596bb%2FssPDIOtherConnectionTasks.png?alt=media)

The following table describes these tasks:

| Task                  | Description                                                                                                                                                                                                                                       |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Duplicate**         | Duplicate the database connection. The duplicate will not be created unless you specify a different **Connection Name** in the Database Connection dialog box when it appears.                                                                    |
| **Copy to clipboard** | Copy the XML defining the step to the clipboard.                                                                                                                                                                                                  |
| **SQL Editor**        | Execute SQL commands against an existing connection within the SQL Editor. See the **Pentaho Data Integration** document for details on the SQL Editor.                                                                                           |
| **Clear DB Cache**    | Clear out the database cache used by PDI to speed up connections. This command is commonly used when databases tables have been changed, created, or deleted (when the information in the cache no longer represents the layout of the database). |
| **Share**             | Share the connection information among transformations and jobs.                                                                                                                                                                                  |
| **Explore**           | Use the Database Explorer to explore the schemas and tables of your connected database. See the **Pentaho Data Integration** document for details on the Database Explorer.                                                                       |
| **Show dependences**  | Show all of the transformations and jobs that use this database connection.                                                                                                                                                                       |


---

# 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.pentaho.com/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-a-pentaho-administrator/define-data-connections/modify-connections/modify-connections-from-pdi.md?ask=<question>&goal=<user_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.
