CODEWITHSUNDEEP
c#sql-serverfull-text-indexing
Dan
Dan

Reputation: 195

Re-build SQL Server Full Text Index

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.

Upvotes: 2

Views: 1872

Answers (1)

Buzz
Buzz

Reputation: 6330

there is no need to delete column ,you just have to recreate the full text indexes you can find the solution here http://msdn.microsoft.com/en-us/library/bb326034(v=sql.105).aspx

Upvotes: 0

Related Questions