This table stores data from the time that the repository was created; therefore, the resulting data set can be huge.
这个表格存储了存储库创建时的数据；因此，结果得到的数据集可能会是巨大的的。
This table contains the live list of work items from the repository, so it is the table that you will use most of the time when you want information about work items.
这个表格包含有来自储存库工作项的列表，这样当您需要关于工作项的信息时，您就会经常用到这些表格了。
Now that you have created an annotated XML schema and registered it into DB2 XML schema repository, you can call into DB2 the XML shredding procedure and start populating your relational table.
至此，已经创建了一个带注释的XML模式，并将其注册到DB 2 XML模式库中，现在可以调用XML分解过程，开始填充关系表。
Table 1: Solution capabilities of an MOF-based central repository.
表1：基于MOF的中央仓库解决方案性能。
Information is stored in table definitions in the DataStage repository.
这些信息存储在DataStage储存库中的表定义中。
You can also save the table definitions to the DataStage repository for future usages.
还可以将表定义保存到DataStage存储库中，以备将来使用。
The Basic Text Search DataBlade module allows you to search words and phrases in an unstructured document repository stored in a column of a table.
基本文本搜索（Basic Text Search）DataBlade模块允许在存储在表列中的非结构化文档库中搜索词和短语。
In this way, a data set in BIRT is just like the information that Rational Team Concert returns from a query: a table of data that is a subset of the information in the repository.
通过这种方式，BIRT中的数据集就像RationalTeam Concert返回至查询的信息一样：一个作为储存库中信息子集的数据的表格。
Percolator was designed to provide cross-row, cross-table ACID-compliant transactions via " snapshot isolation" since many threads on many machines need to transform the repository.
Percolator通过“快照隔离”实现了遵从ACID的跨行及跨表事务，从而满足多线程在多台服务器上对文档库进行转换操作的需求。
In this example, a DataStage table definition named test.Orders is created in the DataStage repository based on the database table schema for the Orders table.
在本例中，根据orders表的数据库表模式在DataStage存储库中创建一个名称为test . Orders的DataStage表定义。
With the table definitions ready in repository, it is time to set up the data source for XML output. There are two options to extract the data.
有了储存库中的表定义，现在可以设置用于XML输出的数据源。
This information, shown in the table below, is required for accessing the CVS repository location where the business processes will be stored.
下表显示了这些信息，它们是访问业务流程在CVS存储库中的存储位置所必需的。
If no team areas exist, no users are listed in the LIVE_CONTRIBUTOR table even if the repository has one or more users.
如果没有团队区域存在，那么在 LIVE_CONTRIBUTOR表格中就不会列出什么用户，就算储存库中拥有一个或者多个用户时也是这样。
Table 1 shows the major system capabilities, which an MOF-based repository should support to allow the manipulation of EA models.
表1显示了基于MOF仓库所支持的，允许对MOF模型进行操作的系统主要性能。
Table 3 shows the repository-related methods of the RedactionToolkitClient class.
表3显示了redactiontoolkitclient类的存储库相关方法。
The fault analysis branch was formed from top-event to bottom event of fault tree. The knowledge was saved in repository with chain table structure.
并用故障树表示故障原因及其传播逻辑关系，从故障树的顶事件至底事件形成故障分析支路，获取的知识以链表的结构存于知识库。
The fault analysis branch was formed from top-event to bottom event of fault tree. The knowledge was saved in repository with chain table structure.
并用故障树表示故障原因及其传播逻辑关系，从故障树的顶事件至底事件形成故障分析支路，获取的知识以链表的结构存于知识库。
应用推荐