您要查找的是不是：
- It will choose indexed access if it has lower cost than table scan. 如果使用索引的开销比表扫描的开销低,优化器将选择索引访问。
- This prevents a large table scan from completely dominating the buffer pool and adversely impacting random operations. 这样可以防止大规模的表扫描完全支配缓冲池,并恶劣地影响随机操作。
- Also, in the logfile, you will notice that the full table scan was performed in this case. 并且，在日志文件中，你将会发现又是执行了全表扫描。
- The optimizer is more likely to choose a full table scan over an index if the value of this parameter is high. 为什么设置高了，优化器会选择全表扫描而不选择索引？
- A table scan running on Node N1 will only fill the memory associated with node N1 unless the scan is being run in parallel on CPUs from multiple nodes. 除非在CPU上对多个节点执行并行扫描,否则,对节点N1执行的表扫描仅填充与节点N1关联的内存。
- However, a table scan could be the most efficient method if, for example, the result set of the query is a high percentage of rows from the table. 但是,如果查询的结果集是占表中较高百分比的行,扫描表会是最为有效的方法。
- If the runtime is incorrect for a table scan or index scan, you may improve performance by executing the REORGANIZE TABLE statement. 如果运行时间对于表扫描或索引扫描不正确,则可以通过执行REORGANIZE TABLE语句来提高性能。
- This means that statistics tied to indexes, which are created with full scan when the index is built, require the whole table scan to be refreshed. 这意味着,对于在生成索引时通过完全扫描创建的索引相关统计信息,将需要刷新整个表扫描。
- When extracting or synchronizing a user, the subscription-list column can cause performance problems as it necessitates a full table scan. 当抽取或同步用户时,由于subscription-list列需要进行全表扫描,所以它可能会导致性能问题。
- The optimizer, in the absence of current statistics, is choosing to do a table scan on both tables involved in the join. 在缺少当前统计的情况下,优化器选择对参与联接的两个表进行表扫描。
- Cumulative count of range and table scans started on the index or heap. 从索引或堆开始的范围和表扫描的累积计数。
- Indexing small tables may not be optimal because it can take the query optimizer longer to traverse the index searching for data than to perform a simple table scan. 对小表进行索引可能不会产生优化效果,因为查询优化器在遍历用于搜索数据的索引时,花费的时间可能比执行简单的表扫描还长。
- As a table grows, you can expect to see some degradation in performance, particularly when table scans are involved. 随着表的逐渐增长,您可能会预料到性能会降低,特别是在涉及到表扫描操作时。
- Or, if table scans are always used to access an index or table, disallowing page-level and row-level locks can help by allowing only table-level locks. 或者如果总是使用表扫描来访问索引或表,那么只允许表级别的锁,而禁止页级别的锁和行级别的锁将会很有帮助。
- With contiguous data pages, DMS tablespaces allow for much more efficient operations such as sequential table scans than SMS tablespaces do. DMS表空间通过连续的数据页面支持比SMS表空间要高效得多的操作,例如连续的表扫描。
- He has planned to lacquer the old table. 他计划给旧桌子上一层漆。
- The lamp fell plonk on the table. 台灯砰的一声倒在桌上了。
- Give the table a good rub with this polish. 用这上光剂把桌子好好擦一擦。
- The petition was ordered to lie on the table. 该请愿书奉命暂搁一边，以后讨论。
- Please give the table a good rub with this cloth. 请用这块布好好擦擦桌子。
