Knowledge Center

Support for adding custom indexes to the ePO database
Technical Articles ID:   KB73614
Last Modified:  4/8/2017


McAfee ePolicy Orchestrator (ePO) 5.x, 4.x


McAfee tries to ensure that product performance meets your needs by providing the necessary database indexes. Despite this, there may be instances where adding specific indexes to the ePO database will further improve performance. It is impossible to proactively ensure compatibility with every possible combination of additional indexes.

Therefore, it is entirely your responsibility to remove all custom-added indexes either during escalation as requested from Technical Support, or prior to installing Proof of Concept builds, hotfixes, patches, or new product versions that created the database tables being modified with your specific indexes. After you have applied the software upgrade, you can add your custom indexes back to the system if required.

There are performance trade-offs when adding indexes. For example, creating an index to improve dashboard display performance could reduce performance when inserting events into the database. It is your responsibility to rectify any performance issues introduced by adding custom indexes.


The content of this article originated in English. If there are differences between the English content and its translation, the English content is always the most accurate. Some of this content has been provided using Machine Translation translated by Microsoft.

Rate this document

Did this article resolve your issue?

Please provide any comments below


This article is available in the following languages:

English United States

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.