> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/reference-docs/reference/server-configurations/database-server-configurations.md).

# Database Server Configurations

| Key                                     | Description                                                                                                                                                                                                                                                                                                                                                                                                   | Default     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| **`db.index.entry.disable`**            | [Enables/disables index entries](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/troubleshoot-elasticsearch.md). If you set to **`true`**, and disable entry indexing, you won’t be able to search entries in the **Search everywhere** search box, but you will be able to view these entries and have filters on them as usual. Disabling entry indexing saves substantial disk space. | **`false`** |
| **`DB.IndexBatchTimeout`**              | The time, in milliseconds, for batch workers to wait for the batch to be full, before indexing. If it does not reach the batch size, it will timeout.                                                                                                                                                                                                                                                         | **`100`**   |
| **`DB.IndexEntryContent`**              | Whether to [index War Room](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/war-room-overview.md#UUID-8981121c-e24a-7b40-52c3-4fe400ecaa19) entries Using Bolt DB.                                                                                                                                                                                    | **`false`** |
| **`DB.MaxIndexBatchSize`**              | The maximum number of items allowed for bleve bolt batch indexing. Define the batch size per index (it is more efficient to index in batches).                                                                                                                                                                                                                                                                | **`100`**   |
| **`DB.MaxIndexQueueSize`**              | The size of the indexing queue when pushing from a go routine into a queue that indexes the data.                                                                                                                                                                                                                                                                                                             | **`50000`** |
| **`index.mapping.total_fields.limit`**  | The maximum total field count in a query using Elasticsearch. Can be used if you experience [feed ingestion issues](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/troubleshoot-elasticsearch.md).                                                                                                                                                                                      | **`1000`**  |
| **`index.query.bool.max_clause_count`** | The maximum amount of clauses a query can contain. Relevant for Elasticsearch version 5.5x (and below) and 6.0 and later. Can be used if you experience [feed ingestion issues](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/troubleshoot-elasticsearch.md).                                                                                                                          | **`1024`**  |
| **`server.data.limit.message`**         | <p>Changes the following default message <strong><code>NOTE, too much data to present, content was truncated</code></strong>.</p><p>This occurs if data is large and the client takes too long to respond when partial data is sent from the server to the client.</p>                                                                                                                                        | N/a         |


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/reference-docs/reference/server-configurations/database-server-configurations.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.