> 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-admin/manage-the-pentaho-system/manage-the-pentaho-server/customize-the-pentaho-server/set-default-select-distinct-for-interactive-reports.md).

# Set default SELECT DISTINCT for Interactive Reports

By default, Interactive Reports queries data with the SQL `SELECT DISTINCT` statement to return only distinct (different) data values, which may require an extensive sorting operation in the database. If you want to reduce the cost of a system-wide sorting operation, you can set new reports to open with the **Select Distinct** option cleared.

Perform the following steps to change the default setting of the **Select Distinct** option in the **Query Setting** dialog box of new Interactive Reports:

1. Stop the Pentaho Server.
2. Locate the `server/pentaho-server/pentaho-solutions/system/pentaho-interactive-reporting` directory.
3. Open the `settings.xml` file with any text editor.
4. Find the `<default-select-distinct>` tag and change it to the desired setting.

   If you want the **Select Distinct** option cleared as the default, set the `<default-select-distinct>` tag to `false` as shown in the following example code:

   ```xml
   <!--  default select-distinct setting for a new report -->
   <default-select-distinct>false</default-select-distinct>
   ```
5. Save and close the `settings.xml` file.
6. Start the Pentaho Server.


---

# 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/pdia-admin/manage-the-pentaho-system/manage-the-pentaho-server/customize-the-pentaho-server/set-default-select-distinct-for-interactive-reports.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.
