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 contains descriptive information about facts.
维度表包含有关事实的描述性信息。
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事实表的一个维度表。
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.
维度表需要作为主键数据的通用键;这将作为事实表的外键。
Each join reduces the size of the fact table by one-tenth due to selectivity of the table filter on each dimension table.
由于每个维度表过滤的选择度,每次连接都会减少事实表大小的十分之一。
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 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 表的索引。
A database option that determines if the application should fully populate the time dimension table when the table is created on first startup.
一个数据库选项,用来决定此应用程序是否应在时间维度表首次启动被创建时完全填充此表。
Otherwise, a new key value is taken from the sequence and used for both, a new entry in the dimension table and as a foreign key in the fact table.
否则,从序列获取一个新的键值,用它作为维表中新条目的主键和事实表中的外键。
A star join query typically involves a fact table and several dimension tables, with join predicates between the fact table and each dimension table.
一个星型连接查询通常包含一个事实表和几个维度表,事实表和每个维度表之间都有连接谓词。
The number of rows selected from each dimension table is less than the number of rows selected from the fact table after all scan filters are applied.
所有的扫描过滤器都应用后,每个维度表选出的行数少于事实表选出的行数。
Also note that the keyword categories are stored in the dimension table category, where each category points to its parent category within this table.
还需注意,关键词类别存储在维表CATEGORY中,在这个表中,每个类别指向它的父类别。
A database option that specifies the number of days (starting from the current date) to pre-populate in the date dimension table when it creates it on first startup.
一个数据库选项,用来指定日期维度表在初次启动被创建时预填充的天数(从当前日期开始)。
Query performance can be improved by leveraging like data types (i.e. INT32 to INT32) when joining foreign keys in a fact table to primary keys in a dimension table.
通过在将fact表中的外键与dimension 表中的主键进行连接时采用like数据类型(例如 INT32 to INT32),可提高查询性能。
应用推荐