Search - One or more crawl databases may have fragmented indices (SharePoint 2013)
Applies to: SharePoint Server 2013, SharePoint Foundation 2013
Topic Last Modified: 2013-12-18
Summary: Learn how to resolve the SharePoint Health Analyzer rule "Search - One or more crawl databases may have fragmented indices."
Rule Name: Search - One or more crawl databases may have fragmented indices
Summary: This article describes the SharePoint Health Analyzer rule for Search service application crawl database defragmentation. The fragmentation of crawl data indexes occurs on a different level than regular disk fragmentation. It occurs in each crawl database as data is created, updated, or deleted during normal crawl activity. When you run the health rule, the system makes used storage contiguous, eliminates unused storage, and compacts the database.
We recommend that you run the crawl database rule under the following circumstances:
If you are using Microsoft SQL Server 2008 Enterprise. Running the crawl database rule automatically enables the Page Compression feature to optimize I/O and disk storage usage.
If significant performance degradation is determined to be caused by crawl database fragmentation. This should be a rare occurrence because crawl databases will usually have some level of fragmentation.
Symptoms: One or more of the following symptoms might appear:
Crawl rate may decrease as more time is spent writing crawl history to the crawl database.
The crawl database defragmentation health rule is run and attempts to correct the fragmentation. Note: when this rule is correcting the fragmentation, the crawl rate is affected. Crawl rate may decrease as more time is spent writing metadata to the property database.
Cause: Fragmentation exists when indexes have pages in which the logical ordering, based on the key value, does not match the physical ordering inside the data file. All leaf pages of an index contain pointers to the next and the previous pages in the index. This forms a doubly linked list of all index/data pages. Ideally, the physical order of the pages in the data file should match the logical ordering. Overall disk throughput is increased when the physical ordering matches the logical ordering of the data.
For more information about database fragmentation, including how to manually detect and repair fragmented indexes, see the SQL Server documentation.Resolution: Enable and run the crawl database defragmentation health rule
Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
In Central Administration, on the home page, click Monitoring.
On the Monitoring page, in the Health Analyzer section, click Review rule definitions.
On the All Rules page, in the Performance section, click Search - One or more crawl databases may have fragmented indices.
If the rule is not enabled, in the Health Analyzer Rule Definitions dialog, click Edit Item on the ribbon. Ensure that the Enabled check box is selected, and then click Save on the ribbon.
On the ribbon, click Run Now.
The rule iterates over all crawl databases in all Search service applications. When it runs, it attempts to perform an online defragmentation first, and then it switches to offline defragmentation where required. In online defragmentation, only the SQL Server leaf pages are defragmented, not the SQL Server locked pages. In offline defragmentation, the locked pages and all the leaf pages are defragmented.
|In SQL Server 2008 Enterprise, the health rule automatically enables the Page Compression feature to optimize I/O and disk usage.|