Platform Deployment Guide › Content Services › Configuring the IDOL Content Database › Disable Search Result Estimates

Disable Search Result Estimates

When you run a content search in the iConsole, the results screen displays the total number of matching events,

By default, this total is an estimate, calculated using an Autonomy IDOL cumulative predictive algorithm. IDOL uses this algorithm to optimize search performance and minimize search times. But if necessary, you can disable this predictive algorithm so that the iConsole results screen displays the actual number of matching events.

To disable estimated totals of matching events, you edit the content database configuration file and extend the query timeout. However, if you do disable estimated totals, content searches may take longer to complete.

Note: Do not confuse the total number of matching events with the total number of search results. By default, iConsole searches are capped. This means, for example, that a search may only return 100 results even if there are more events than this in the CMS database that match the search criteria. If necessary, you can override the search capping to display all matching results. See the iConsole online help for details.

To disable estimates of total matching events

1. Stop any content indexing jobs that are currently running.
2. Stop the CA DLP Content Database service.

   While this service is stopped, you cannot run content searches.

   This service runs on the server hosting the content database.

3. Edit the content.cfg configuration file.

   Find this file on the server hosting the content database. The file is in the \Content\IDOL folder below the CA DLP installation folder.

4. Add the following line to the [Server] section of content.cfg.

   TotalResultsPredictionThreshold=0
   

5. Restart the CA DLP Content Database service.
6. Extend the query timeout for content searches.

   The query timeout defaults to 30 seconds. Content searches take longer to return results if you disable estimated results totals. We therefore recommend that you extend the query timeout.

   1. Edit the registry on the server hosting the IDOL connector framework and content database.
   2. Go to the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates
        \CA DLP\CurrentVersion\Content Services\IDOL Provider
      

   3. Modify the QueryTimeoutSecs registry value.

      Because content databases vary in size, we cannot give specific recommendations for the new timeout value. Investigate different timeouts until you discover the optimal timeout for your content database.