Time dimension table, containing 10,000 rows.
Time维度表包含10,000行。
Customer dimension table, containing 10,000 rows.
Customer维度表包含10,000行。
Location dimension table, containing 10,000 rows.
Location维度表包含10,000行。
A dimension table should contain no facts, only metadata.
维度表可能不包含事实，而只包含元数据。
A dimension table contains descriptive information about facts.
维度表包含有关事实的描述性信息。
The third method is to add a field to the dimension table that captures old values.
第三个方法是，在捕获旧值的维度表中增加字段。
This must be the only key necessary to relate the fact table to the dimension table.
此键必须是需要关联事实表和维度表的唯一的键。
As you're designing your dimension table, you need to plan for changing dimensional data.
在设计维度表时，需要计划变更维度数据。
This query plan uses hash join for each join between the fact table and a dimension table.
这个查询对每个事实表和维度表之间的连接使用散列连接。
For example, as shown below, the Location table is a dimension table for the Orders fact table.
例如，如下所示，location表是Orders事实表的一个维度表。
The entire fact table is read if all dimension table joins are removed by this optimization.
如果所有的维度表连接被该优化移除，则会读取全部事实表记录。
To capture previous values, some sites add three or four fields when they build the dimension table.
为捕获从前的值，在构建维度表时，一些站点需要增加3个或4个字段。
Generally speaking, a dimension table should be denormalized and flat, with as many columns as needed.
一般说来，维度表应该被非规范化和扁平化，并根据需要使用大量列。
Assume that there is a LINEITEM fact table on one remote source and a PART dimension table on another.
假设在一个远程数据源上有一个lineitem事实表，在另一个远程数据源上有一个part维表。
It's a right-deep query plan such that for each hash join, the build table is a small dimension table.
每个散列连接都是右深查询，构建的表是一个小的维度表。
Using the previous example, an XML column might be used in the dimension table containing product data.
对于上述示例，可以在包含产品数据的维表中使用一个xml列。
Since the interest rate is an attribute of Account table, the Account dimension table needs to be added.
因为利率是account表的一个属性，所以需要添加account维度表。
The join between the fact table and any dimension table is an equi-join, which makes a hash join possible.
事实表和任何维度表之间的连接都是等值连接，这使得散列连接成为可能。
The level of a dimension table corresponds to number of links it needs to connect to the central fact table.
维度表的层次与它需要连接到中心事实表的连接数目有关。
One of the most important design decisions you face is how to capture hierarchy information in a dimension table.
您所要面对的最重要的设计决策之一，是如何捕获维度表的层次结构信息。
A dimension table needs a generalized key as the primary key data; this becomes the foreign key in the fact table.
维度表需要作为主键数据的通用键；这将作为事实表的外键。
When a join is executed that incorporates an index that is selective, any column in the dimension table can be used.
当连接执行时，合并选中的索引，此时维度表中的任何列都可使用。
Each join reduces the size of the fact table by one-tenth due to selectivity of the table filter on each dimension table.
由于每个维度表过滤的选择度，每次连接都会减少事实表大小的十分之一。
However, it could have its own dimension table, a region table, that separates different locations into distinct regions.
然而，它也可以拥有自己的维度表region，以将不同的Location放到不同的区域。
If so, the existing ID is read from the dimension table and used as the foreign key for the new entries in the fact table.
如果是，则从维表中读取已有的ID，并用它作为事实表中新条目的外键。
You can choose to have one such dimension table for each standard category, such as subject-description, country, and organization.
可以选择为每个标准类别使用一个这样的维表，例如主题描述、国家和组织。
The performance improvement depends on the selectivity of the filter on the dimension table from which the join keys are pushed down.
性能的提高取决于连接键被下推时所在维度表的过滤选择度。
You can define the many-to-one relationships among members within a dimension table as a separate dimension table, forming a hierarchy.
您可以将一个维度表中成员之间多对一的关系定义为一个单独的维度表，从而形成层次结构。
The member key column for the lowest level of the dimension must contain the keys that relate the fact table and the dimension table.
对应着维度最低级别的成员键列必须包含关联事实表和维度表的键。
The location_id join keys that meet the filter requirements on the Location dimension table are pushed down to the index on the Orders table.
Location维度表中满足过滤条件的 location_id连接键被下推至Orders 表的索引。
应用推荐