SQL Server Full-Text Index Questions

Question

5.00/5 (2 votes)

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

Dan Jurden

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Ganesan Senthilvel · Answer 1 · 2012-06-19T18:47:00

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[^]