SQL Server全文索引问题 [英] SQL Server Full-Text Index Questions

问题描述

我有一个客户正在其应用程序中使用全文本索引.他们通过应用程序重建索引.当他们这样做时，手动从目录中删除所有列.然后他们将它们全部添加回去.之后，他们开始一个新的增量人口.

在此过程之后，它们通常以损坏的索引结尾.当他们执行应该返回数据的搜索时，什么也不会返回.甚至在人口完成之后.因此索引已损坏.他们找回它的唯一方法是在SQL Server管理工具中重建索引.

它们在目录中具有许多(20-50或更多)列和表.如果目录中存在次数，建议数量是否有限制?他们应该将其分解为较小的目录吗?

他们应该通过删除所有列并将其重新添加来重建索引吗?或者，还有更好的方法?还是只是发送ALTER REBUILD命令是更好的方法?

预先感谢.

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.

推荐答案

对于每个行级失败，爬网日志都包含有关失败原因的详细信息.错误计数在完整填充或增量填充的末尾汇总.

还有其他一些故障可能会影响索引编制过程本身并阻止总体完成:

*全文索引超出了全文目录中可以包含的行数限制.
*被索引表上的聚集索引或全文索引索引会被更改，删除或重建.
*硬件故障或磁盘损坏会导致全文目录损坏.
*包含正在被全文索引的表的文件组脱机，或者被设置为只读.

您应该在任何重要的全文索引填充操作的结尾或发现填充未完成时查看爬网日志.

请参阅全文索引文章，网址为: SQL全文搜索编程 [ ^ ]

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

这篇关于SQL Server全文索引问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！