Q：如何计算已分区表（或者任何相关的表）的表大小和索引大小？
Q: How do I calculate the table and index size for a partitioned table (or any table for that matter)?
自动表重组不会考虑那些表大小估计值大于大小条件的表。
Tables whose estimated size is greater than the size criteria are not considered by automatic table reorganization.
优化器使用表大小、索引可用性以及数据分布等信息来确定响应该查询的最佳路径。
The optimizer USES information such as table sizes, availability of indexes, and data distribution to figure out the optimal way to answer the query.
由于每个维度表过滤的选择度，每次连接都会减少事实表大小的十分之一。
Each join reduces the size of the fact table by one-tenth due to selectivity of the table filter on each dimension table.
然而，如果将它设置的太大，则可能会由于为该分区创建的页表大小而浪费所管理系统上的宝贵内存资源。
However, if you make it too large, you can waste valuable memory resources on your managed system due to the size of the page table created for the partition.
非常深刻的前向后一小车床进行鞍几乎镗表大小的T型槽交叉幻灯片装有“桥梁支架”在前面。
Unusually deep front to back for a small lathe the saddle carried an almost boring-table sized T-slotted cross slide fitted with a "bridge bracket" at the front.
您可以随时更新时间的状态栏，然后单击确定，然后它将改变你的哈希表大小保存为32M到64m。
You can update seconds on status bar and click OK, then it will change to your choice. Hash table size: recommend to 32m to 64m.
如果索引的使用效率很低，或者根本就不能使用索引，则会减慢查询速度，而且随着服务器上的负载和表大小的增加，这个问题会变得更加显著。
Inefficient use of indexes, or not being able to use indexes at all, slows the queries, and this issue becomes more pronounced as the load on the server and the size of the tables increases.
你会发现，使用任何现有的简单“噪音表”，被判定为发出同样大小噪音的车辆，在表上可能显示出相当大的差异。
You find that with any existing simple "noise-meter", vehicles which are judged to be equally noisy may show considerable difference on the meter.
如果有一些具有不同页大小的表空间，那么每种页大小必须至少有一个缓冲池。
If there are table Spaces with different page sizes, there must be at least one buffer pool per page size.
对于具有大于一个页面大小的表空间的数据库而言，需要创建具有匹配页面大小的附加缓冲池。
For a database that has table Spaces of more than one page size, additional buffer pools with matching page sizes need to be created.
还可以修改表的大小（每个页面上的条目数量）和数据刷新频率以满足自己的需要。
The size of the table (number of entries per page) and data refresh rates can also be changed to meet the your needs.
跨多个分区划分数据库将允许您根据环境中分区数目的因数来增加表的最大大小。
Partitioning a database across multiple partitions lets you increase the maximum size of your table by a factor of the number of partitions in your environment.
一般来说，DB 2根据最大物理分区的大小将表空间分成逻辑上的几块。
Normally DB2 divides the table space into logical pieces based on the size of the largest physical partition.
请注意，缓冲池和表空间的页大小都是8K，两者是相同的。
Note that the page sizes of 8K for the buffer pool and table space are the same.
在DB 2中，表和表空间的大小限制是根据每个分区进行规定的。
Table and tablespace size limits in DB2 are on a per partition basis.
这种设计并不可取，因而必须加以改进以确保控制好档案表的大小。
This design is not desirable, and must be refined to ensure that the size of the archive table is kept under control.
两个表均存储在页面大小为32 - KB的表空间中来最大化需要读取大量行的性能分析查询。
Both tables are stored in table Spaces with a 32-kb page size to maximize the performance analytical queries that read large Numbers of rows.
GPT默认支持128个分区，当然您也可以更改分区表的大小，如果您的分区软件支持这种更改的话。
By default, 128 partitions are supported, although you can change the partition table size if the partitioning software supports such changes.
为函数添加此附加功能的方法非常简单：提供名为nrows和ncols的两个输入参数，允许在调用函数时更改乘法表的大小。
This additional power was simple to include in the function: You provide input parameters named nrows and ncols that allow the size of The Times table to be changed when the function is invoked.
升级cell1的模式，包含升级表扩展大小和修改原表结构。
Upgrade schema for cell1, including upgrading tables extent sizes and modifying old table structures.
然后它会为每个集合生成一个表，并按照集合大小排序，其中最频繁使用的大小排在前面。
It then produces a table for each collection sorted by size of collection, with the most frequent size first.
没有必要拥有多个具有相同页大小的临时表空间，通常只需一个具有最大页大小的临时表空间就够了。
There is no reason to have more than one temporary table space of the same page size, and usually one with the largest page size is sufficient.
在数据仓库中，事实表或历史表的大小是摆在设计人员和管理员面前的一个挑战。
In data warehouses, the size of fact tables or history tables poses challenges to designers and administrators.
您可以选择通过不存储极其频繁重复的文本字段，而是将其一次性放置在一个子维度表中，节省该大小的表中的大量空间。
You can expect to save quite a bit of space in a table of that size by not storing the very frequently repeated text fields, but rather putting them once in a subdimension table.
这样可以确保能够在32K页面大小的表空间中创建任何行大小超过4 K字节的用户表。
This ensures that any user tables whose row size exceeds 4k bytes is successfully created into a 32k page size tablespace.
用DB 2创建的默认数据库拥有一个4K页面大小的表空间。
A default database created by DB2 has a tablespace with a 4k page size.
DB 2V 9引入了一个表分区特性，它能够增加一个表的可能大小，同时能够显著减少管理大型数据库所需要的维护。
DB2 V9 introduced a table partitioning feature that can increase the potential size of a single table, and significantly reduce the maintenance effort required to manage very large databases.
取决于您的数据库，您可能想要不同的页面大小，它与您的源表页面大小一致。
Depending on your database you may want to have a different page size that matches the page size of your base source tables.
一个问题是，这种表的大小要比普通表增长得快，可能会导致一些严重的性能问题。
For one, they grow much faster than normal tables and thus can cause some serious performance issues.
应用推荐