If your Meridian server uses the Indexing Service instead of Windows Search, a content index is created the first time AMFTFilter processes a vault. The index is updated with new and changed documents each time AMFTFilter runs thereafter. If you created a scheduled task for the vault when you configured content indexing as described in Configure Content Indexing, the task will maintain the index.
However, if this is an existing vault containing many documents, building a new catalog may take a long time. Depending on the server hardware, the type of files being indexed, and the IFilter used, it will take approximately one hour to index every 10,000 documents. This might require more time than is available between the time the scheduled task starts and production vault access next begins. This means that the search catalog will still be processing, impairing the performance of the Meridian application server and, conversely, any production activity will impair the performance of catalog processing, thus delaying its completion. Therefore, we recommend that you build the new catalog when there will be plenty of time for the catalog to process before production hours begin, for example, during a weekend.
To build a content index:
