当我改变代码并尝试保存，日食开始重新索引库。
When I change the code and try to save, eclipse starts to re-index the repository.
可以在查询之前，转到Index选项卡来重新索引您的文档。
You can switch to the index TAB to re-index your documents before you query them.
可以肯定的是，只是手动重新索引在后台，看看你的产品出现在前面的或不。
To be sure, just manually re-index it in the Backoffice, and check whether your products appears in front or not.
保存对主模板的更改，并重新访问应用程序的索引页面。
Save your changes to the master template, and revisit your application's index page.
没有必要在恢复索引以后重新启动服务器。
It is not necessary to restart the server after restoring the index.
另外的解决方案，取决于具体的错误，可能是手工重建非聚簇索引，如果数据是静态的手工扔掉和重新载入表，诸如此类。
Additional solutions, depending on the errors, may be to manually rebuild non-clustered indexes, manually drop and reload a table if the data is static, and so on.
此外，如果您认为问题是由于坏的索引，那么试图重新创建数据库的全文本索引(如果可能的话)。
Also, try to recreate the database's full-text index, if possible, if you think the problem is due to a bad index.
在该页面被重新抓取和索引之后，搜索结果及更新后的摘要及缓存页面(基于新内容)将可见。
After the page has been re-crawled and re-indexed, the search result with an updated snippet and cached page (based on the new content) can be visible.
然后，重新访问应用程序的索引页面，您将看到如图6所示的内容。
Then, revisit the application's index page, and you should see something that looks like Figure 6.
在这种情况下，重新组织索引可能会影响DB2的选择，可能产生性能更好的查询访问路径。
In that case, reorganizing the index might lead to its selection as part of a better-performing query access path.
为了减少争用，DROP并使用RANDOM选项重新CREATE索引。
To reduce contention, DROP and re-CREATE the index using the RANDOM option.
因此，需要有规律地运行runstats并重新绑定数据库，以确保数据库索引不会过期。
Therefore, running runstats and rebinding the database need to be done regularly to ensure that database indexes are not out of date.
B - TreeScanner线程会去掉删除的索引项并重新平衡索引节点。
The B-Tree Scanner threads remove deleted index entries and rebalance the index nodes.
重新生成索引的速度更快(让未改变的部分保持打开)并且读取索引时的并发性更好(使用了只读标志)。
Faster index reopening (keeps unchanged segments opened) and better index reader concurrency (use of the read only flag).
重新构建视图时，这些索引会占用服务器上的磁盘空间和处理时间。
These indexes take up disk space and processing time on the server when the views are rebuilt.
因此，如果索引超过四层，那么您可能需要考虑删除一些层或用较少的层次来重新构建它，以便获得更好的性能。
Thus if any index has more than four levels, you may need to consider dropping and rebuilding it with fewer levels for better performance.
使用字节索引值来代替标记的策略在某种程度上减少了重新构造后的文档的大小，但也限制算法只能处理不同标记数少于254的DTD。
The strategy of using byte index values in the place of tags reduces the size of restructured documents somewhat, but also limits the algorithm to handling DTDs with fewer than 254 distinct tags.
这意味着，DB 2从重新构建和增量索引维护两种方法中选择最合适的方法。
This means that DB2 chooses either the rebuild or incremental index maintain approach, whichever is the best fit.
它通过扫描所有XML文档重新构建所有索引。
It rebuilds all the indexes by scanning all the XML documents.
您可以通过下面的与在原始用户数据库上创建索引一样的步骤来对多行文本域进行重新检索。
You can re-index the multiline text fields by following the same procedures used to create the indexes on the original user database.
庞大的存储库重新生成索引需要花费大量的时间。
Index regeneration with a large repository can take an extended amount of time.
如果您决定删除索引，那么首先要保存它的CREATEindex语句，以便在需要时轻松地重新创建它。
If you do decide to drop an index, you should first save its create index statement so that you can easily recreate it if necessary.
如果按照指定的方法不能合法地使用索引，则重新创建索引。
The index is recreated if it is not valid to use using the specified approach.
当这样设置索引选项时，仅当用户按f 9或单击蓝色的重新加载箭头时，才刷新视图。
When the indexing options are set this way, the view is refreshed only when a user presses F9 or clicks the blue reload arrow.
终止和重新创建索引禁用的外键之后，降级就成功完成了。
After the foreign key constraint with index disabled is dropped and recreated, the reversion completes successfully.
另外还需要收集统计信息，重新构建所有无效的索引。
The statistics need to be collected and all invalid indexes rebuilt.
这些冲突操作包括：压缩、重新打包、收缩、更改、在线索引构建、截断、以及删除。
These conflicting operations include: compress, repack, shrink, alter, online index build, truncate, and drop.
在去年我们就准备好最后一击：重新爬行(索引)过所有已生成的知识形式并且重新启动系统。
By last year we were ready for the final push: re-crawling all the generated knowledge representations and restarting the system from near scratch.
移动数据库时重新检索：只要用户的数据库被移动，支持多行文本域的索引就会丢失。
Re-index when moving databases:Whenever user databases are moved, the indexes that support multiline text fields are lost.
要想进行更改，必须删除索引，然后重新创建它。
You would need to drop the index and create it again in order to implement changes.
应用推荐