索引重组和索引重建主要区别有哪些？
What are the primary differences between an index reorganization and an index rebuild?
将索引重建索引当我启用约束后导入数据？
Will index rebuilds it indexes when I enable constraints after importing data?
索引重建始终将重建整个索引，而无需考虑的碎片的程度。
An index rebuild will always rebuild the entire index, regardless of the extent of fragmentation.
另外的解决方案，取决于具体的错误，可能是手工重建非聚簇索引，如果数据是静态的手工扔掉和重新载入表，诸如此类。
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.
这个特性提高了hdr主服务器的可用性，因为与停止服务并在主服务器上重建索引相比，复制索引要快得多。
This feature increases the availability of the HDR primary server because replicating an index is quicker than dropping and then rebuilding the index on the primary server.
这时，将重建索引，并且会验证对象。
The indexes will be rebuilt at this time, and the objects will be validated.
除非完全重建视图索引(按Shift +F9)，否则这样将阻止变更出现在视图中，而且还会导致将更新复制到本地副本的操作失败。
This prevents the changes from showing up in views unless the view index is completely rebuilt (press Shift + F9), and it also causes replication of updates to local replicas to fail.
如果您想那三个谓词完全按照它们的编码顺序应用，则必须删除并在(COLA,COLC,COLB)上重建索引(或者创建一个新索引)。
If you want those three predicates applied in the exact order in which you code them, you must drop and re-create the index (or create a new index) on (COLA, COLC, COLB).
由于每个索引(片段)都有自己的udi计数器，因此将根据索引(片段)的修改程度判断是否跳过或是重建索引统计。
Since each index (fragment) has its own UDI counter, the decision to skip or rebuild index statistics is done based on how much the index (fragment) has changed.
在这种情况下，您应该重建搜索索引编录。
In this situation, you should rebuild the search index catalog.
在ServerConfiguration文档中设置 Log_update=2，以便记录索引程序何时刷新/重建视图。
Set Log_update=2 in your Server Configuration document to record when the Indexer refreshes/rebuilds views.
比较原始文档的修改日期，看是否有必要重建索引。
A modification date compare against the original Document's modification date, to see if it needs to be reindexed.
在重建过程中，当通过联合将大量的内容载入WorkplaceWebContentManagement时，经常需要手工重新生成索引。
Manual index regeneration is often required when a large amount of content has been loaded into Workplace Web content Management through syndication during a rebuild.
索引与表不匹配。请删除该索引文件然后重建索引。
Index does not match the table. Delete the index file and re-create the index.
有时候它将会重建这个索引来确保它是最新的，同时可以了解从最近一次检查以来哪些包已经被升级或者加进了频道。
Sometimes it will 're-build' this index to make sure that it is up to date and knows which packages have been upgraded or added into the channel since it last checked.
我已经实现了一个索引维护计划，检查和重建这些指标，必要时每隔几小时。
I have implemented an index maintenance plan that checks and rebuilds these indexes when necessary every few hours.
需要独占可写权进行结构索引的重建工作。
Need EXCLUSIVE writeable access to rebuild structural index.
然而，这些指标的碎片严重和我结束了相当频繁的延迟尖峰由于重建索引等因素的影响，我不明白。
However, these indexes fragment badly and I end up with pretty frequent delay spikes due to rebuilding indexes and other factors that I don't understand.
这有助于，当然增加了查询响应时间的尖峰，每当重建索引，我想避免或减少。
This helps, but of course adds spikes in query response times whenever the indexes are rebuilt which I would like to avoid or minimize.
重建需要除去旧之前建立新的索引。
REBUILD requires building the new index before dropping the old one.
在这种情况会更好一些，只需重建索引。
重建将自动重建所有索引列统计信息，而重新组织根本不会更新统计信息。
REBUILD will automatically rebuild all index-column statistics, whereas REORGANIZE won't update statistics at all.
请删除该索引文件然后重建索引。
lob索引是内部结构，同lob存储紧密联系，这意味看用户无法删除并且重建lob索引。
The LOB index is an internal structure that is strongly associated with LOB storage. This implies that a user may not drop the LOB index and rebuild it.
你可以创建一个压缩索引，或者重建时压缩一个索引(尽管对在线重建、重建分区索引等有一些限制)。
You can create an index as compressed, or rebuild it to compress it although there are some restrictions about online rebuilds, rebuilds of partitioned indexes etc.
你可以创建一个压缩索引，或者重建时压缩一个索引(尽管对在线重建、重建分区索引等有一些限制)。
You can create an index as compressed, or rebuild it to compress it although there are some restrictions about online rebuilds, rebuilds of partitioned indexes etc.
应用推荐