Click here to Skip to main content
13,000,569 members (60,185 online)
Rate this:
Please Sign up or sign in to vote.
See more:
I have a client who is utilizing full-text indexing in their application. They rebuild the indexes via the application. When they do this, the manually remove all columns from the catalog. Then they add them all back. After doing that they start a new Incremental Population.

After this process they often end up with corrupted indexes. When they perform searches that should return data, nothing is returned; even after the population is complete. So the index is corrupt. The only way they can get it back is to rebuild the indexes in SQL Server Management Tools.

They have many (20-50 or more) columns and tables in a catalog. Is there a recommended limit to the number if times in a catalog? Should they break this up into smaller catalogs?

Should they be rebuilding the indexes by removing all columns and adding them back? Or is there a better way? Or is just sending an ALTER REBUILD command the better way?

Thanks in advance.
Posted 19-Jun-12 4:14am

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

For each row-level failure, the crawl log contains details on the reason for the failure. The error counts are summarized at the end of a full or incremental population.

There are other failures that can impact the indexing process itself and prevent the population from completing:

* The full-text index exceeds the limit for the number of rows that can be contained in a full-text catalog.
* A clustered index or full-text key index on the table being indexed gets altered, dropped, or rebuilt.
* A hardware failure or disk corruption results in the corruption of the full-text catalog.
* A file group that contains the table being full-text indexed goes offline, or is made read-only.

You should view the crawl log at the end of any significant full-text index population operation, or when you find that a population did not complete.

Refer the full text index articles at: SQL Full Text Search Programming[^]

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Mobile
Web01 | 2.8.170624.1 | Last Updated 20 Jun 2012
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100