> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/settings/dimension-indexing.md).
# Dimension Indexing
Set how many values of each dimension Tellius indexes for Search and Kaiya, how fast indexes are built, and check or rebuild the index of a dataset or Business View.
Under **Settings → Modules → Data → Dimension Indexing**, administrators control the dimension index: the list of column values that Search and Kaiya look up to recognize the values people type in a question, such as a product, region or account name. Only the values of indexed columns are considered when Tellius works out what a question refers to.
The page has two parts. **Dimension index configuration** holds three workspace-wide limits. **Manage data indexing and optimization** lets you pick one dataset or Business View, see how many values are indexed for it, and start a reindex.
{% hint style="info" %}
**Coming from an earlier release?** In releases before Tellius 6.4, these settings were under **Settings → Application Settings → Dimension Indexing** (also called **Data Index**). In Tellius 6.4, they are on this page, and **Save** at the top right applies the limits.
{% endhint %}
### Dimension index configuration
Each column has an index setting in the Metadata view of a dataset: **Index**, **Enhanced Index** or **Don't Index**. The two limits below decide how many unique values Tellius indexes for those columns. See [Metadata view](/tellius-6.4/data/preparing-your-datasets/metadata-view.md).
* **Enhanced Index limit:** the most unique values Tellius indexes for a column set to **Enhanced Index**. Use enhanced indexing for high-cardinality dimensions, such as customer, account or SKU names, where people need to ask about any one of many values. Values above 100,000 can slow down Search and Kaiya.
* **Default Index limit:** the number of unique values Tellius indexes for a column set to **Index**, the usual setting. It balances answer quality and speed for typical dimensions.
* **Pagination:** how many records Tellius reads from the data source at a time while it builds an index. A higher number builds indexes faster but uses more memory. A lower number is slower but easier on the system.
Each field accepts a whole number from 1 to 2,147,483,647. Type a value or use the up and down arrows. A larger value is brought down to the upper limit instead of being rejected.
{% hint style="success" %}
**Which limit to raise?** If Kaiya or Search doesn't recognize a value that is in your data, check how the column is indexed first. For one or two columns with many values, set them to **Enhanced Index** in the Metadata view rather than raising **Default Index limit** for every column. Raise **Enhanced Index limit** only as far as those columns need, because very large indexes slow down answers. Lower **Pagination** if indexing jobs put too much load on the system.
{% endhint %}
**Cancel** and **Save** at the top right become active once you change a limit. **Save** applies the new limits, and a message confirms the update. **Cancel** restores the saved values. If you leave the page with unsaved changes, Tellius asks whether to keep editing or discard them.
### Manage data indexing and optimization
Use this part to check the index of one dataset or Business View, or to rebuild it. It works in three steps.
1. **Choose the type.** Select **Dataset** or **Business View**, then select **Continue**.
2. **Choose the item.** Open the list and pick the dataset or Business View. Type in the search box at the top of the list to narrow it down. Select **Continue**, or **Back** to change the type.
3. **Manage the index.** The **Current selection** card shows the item you chose and its type. Below it, **Index Management** has two actions:
* **Check Indexes:** looks up how many values are indexed for this item and shows the count under the button. It only reads the index and changes nothing.
* **Start Reindex:** starts a job in the background that rebuilds the index for this item. A message confirms that the job has started. You can keep working while it runs.
For a Business View, **Index Management** also shows the **To re-index associated datasets** checkbox. Select it before **Start Reindex** to rebuild the indexes of the datasets that the Business View is built on as well.
Select **Start Over** to go back to the first step and pick another item.
{% hint style="success" %}
**When to reindex.** Rebuild the index after you change a column's index setting or a limit, or when Kaiya or Search keeps missing a value that you know is in the data. Use **Check Indexes** first: a count far below the number of values you expect points to an indexing problem. For a Business View that joins several datasets, select **To re-index associated datasets** so every source is rebuilt in one go.
{% endhint %}
### Who can see this page
Administrators and super users see **Dimension Indexing** in Settings. A custom role reaches it with **Manage workspace** under **Administration**. See [Custom roles](/tellius-6.4/settings/users-and-access/custom-roles.md).
### Related pages
* [Metadata view](/tellius-6.4/data/preparing-your-datasets/metadata-view.md)
* [Storage & Cache](/tellius-6.4/settings/storage-and-cache.md)
---
# 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://help.tellius.com/tellius-6.4/settings/dimension-indexing.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.
