例如，在下面的部门表中，我们为每个部门使用一个XML文档（中等粒度）。
For example, in our department table below, we use one XML document per department (medium granularity).
但是，您总是可以上卷(汇总)数据以创建一个略粗的粒度级别的表。
You can, however, always roll up (summarize) the data to create a table with a less detailed level of granularity.
内容类型的粒度是表级别的而不是行级别的。
The granularity of the content type is to the table level rather than the row level.
改变表的锁定粒度。
注1：对于Transactions历史表上的mdc维，另一种设计方案是以更细的粒度定义Transaction日期，例如每周或每天。
Note 1: an alternative design for the MDC dimension on the Transactions history table is to define Transaction date at a smaller granularity, such as by week or by day.
由于可以在表空间级进行备份，所以还可以进行粒度控制。
You also have granular control since you can back up at the table space level.
这就是您的用户将制定决策的方式—比较来自不同粒度的不同事实表的事实。
This is how your users are going to make decisions-by comparing facts from different fact tables with different grains.
例如，一个存储过程可以按照一个粗粒度级别描述，其中源或目标指向数据库表。
For example, a stored procedure can be described on a coarse-grained level where sources or targets point to database tables.
设计细粒度的类层次和粗粒度的数据表。
Design fine-grained class hierarchy and coarse-grained database tables.
因为片段统计比表统计更加细粒度，因此会占用更多的空间。
Since the fragmented statistics are more granular than table statistics, they do take up more space as well.
表2根据其用于细粒度组件模型还是粗粒度组件模型对各个组件技术进行了大体归类。
Table 2 categorizes, in general, the various component technologies in terms of their usage as fine - or coarse-grained component models.
细粒度的数据表意味着更多数据表连接，相应的查询也会更复杂。
Having fined-grained database tables means more table joins and accordingly more complex queries.
如果您尝试修改一个表，以便使用这种锁粒度选项，而那个表又不是mdc表，那么您将收到一个SQLSTATE 628n错误。
If you attempt to alter a table to use this lock size option, and it isn't an MDC table, you will receive an SQLSTATE 628n error.
汇总表的另一个好处是支持对有不同粒度的两个事实表(甚至可能位于单独的数据市场中)进行比较。
Another benefit of summary tables is that they let you compare results from two different fact tables (maybe even in separate data marts) that have different grains.
表3.1中的主题包含了粗粒度的待办项。
表1根据其用作细粒度组件模型还是粗粒度组件模型对各种组件技术进行了大致归类。
Table 1 generally categorizes the various component technologies in terms of their usage as fine- or coarse-grained component models.
细粒度的POJO和粗粒度的数据表。
耐火砌泥的物理及化学参数以及粒度分布应该满足表28中指定的要求。
Physical and chemical parameters and grain size composition of mortar shall meet requirements specified in table 28.
我们可以改变矩阵的“粒度”或细节水平，使得每一行代表与一个业务流程相关的单个事实表(或立方体)。
We can alter the matrix's "grain" or level of detail so that each row represents a single fact table (or cube) related to a business process.
一旦我们指定的单个事实表中，我们可以列补充矩阵列来表示事实表的粒度和相应的事实(确切，计算或预示)。
Once we've specified the individual fact table, we can supplement the matrix with columns to indicate the fact table's granularity and corresponding facts (actual, calculated or implied).
事务粒度事实表装载。
累积快照粒度事实表装载。
周期粒度事实表装载。
美国在1982年发表了“具体和迫击炮用于粉磨高炉矿渣细粒度”标准（美国ASTMC989- 82 ） ，并于1989年进行了修订。
The United States in 1982 issued a "concrete and mortar used for grinding blast furnace slag fine-grained" standard (ASTM C989 - 82), and was revised in 1989.
美国在1982年发表了“具体和迫击炮用于粉磨高炉矿渣细粒度”标准（美国ASTMC989- 82 ） ，并于1989年进行了修订。
The United States in 1982 issued a "concrete and mortar used for grinding blast furnace slag fine-grained" standard (ASTM C989 - 82), and was revised in 1989.
应用推荐