运行下面的命令，如图11所示，将演示数据导入维度表activity、DEPARMENT、PROJECT和D _ TIME以及事实表humancost中。
Run the following command, as seen in Figure 11, to import demo data into dimension tables ACTIVITY, DEPARMENT, PROJECT, and D_TIME and fact table HUMANCOST.
这段代码从清单9所示的XML文件中读取数据，然后将它变为表格格式。
This code reads data from the XML file shown in Listing 9 and formats it into a table.
在创建扩展映射文档以沿着样例存储过程STG_TO_DWH跟踪沿袭后，生成了如图3所示的正确的数据沿袭报告。
Figure 3 shows the corrected data lineage report after creating an extension mapping document to track the lineage through the example stored procedure STG_TO_DWH.
这些代码生成如清单8所示的JSON数据，假设给出了一个错误条件。
This code generates the following JSON data shown in Listing 8, assuming an error condition is present.
首先检索这些界面的数据，如清单2所示。
First, retrieve the data for these interfaces as shown in Listing 2.
输入图9所示的数据。
本技巧中使用的实例数据如清单1所示。
The instance data you'll use in this tip is shown in Listing 1.
假设它从表1所示的表中获取包含数据值的两个行。
Assume it retrieves two rows containing the data values in the customer table as shown in table 1.
下一个页面就是list . php页面，如清单6所示，它返回数据库中的提要列表。
The next page is the list.php page, in Listing 6, that returns the list of feeds in the database.
表dw_books中应该包含表3所示的数据。
You should have something like the data in table 3 in your dw_books table.
功能性映射Func_Line1作为输入卡in1接收清单34所示的数据。
The Functional map Func_Line1 receives the data shown above in Listing 34 as input card In1.
假设您具有如图12所示的数据库结构(查看图12的文字版本)。
Consider that you have the database structure in Figure 12. (View a text-only version of Figure 12.)
xsd (xmlSchema)，如清单4所示；customer3 . xml (xml数据)，如清单12所示。
(XML schema) in Listing 4, customer3.xml (XML data) in Listing 12.
xsd (xmlSchema)，如清单5和清单6所示；customer4 . xml (xml数据)，如清单13所示。
Company4.xsd (XML schema) in Listing 5 and Listing 6, customer4.xml.
xsd (xmlSchema)，如清单2和清单3所示；customer2 . xml (xml数据)，如清单11所示。
Company2.xsd (XML schema) in Listing 2 and Listing 3, customer2.xml.
这些输入和输出可以是纯控制流链接(类似于上一部分中的模型)，也可以是类似于图5所示的数据流链接。
The inputs and outputs can be pure control-flow links as in the models in the previous section, or can be data flow links as shown in Figure 5.
故障发生后，如图3所示，数据库和协调器最后可能会重新启动并使用恢复日志和恢复规则来确保数据完整性。
After the failure, the databases and the coordinator can eventually restart and use their recovery logs and recovery rules to insure data integrity as illustrated in Figure 3.
正如图7所示的邮件发送数据，这可以清楚展示集群活动随时间变化发生的所有变化。
Just like the mail delivery data in figure 7, this can clearly show any changes in your clustering activity over time.
如图2和图3所示，元数据浏览器根据用户选择的操作显示不同的对象集合，包括定制对象。
As shown in Figure 2 and Figure 3, different sets of objects, including custom objects, are displayed based on user-selected operations.
这10个字节可能包含垃圾数据，如图1所示。
The 10 bytes might contain garbage data, as shown in Figure 1.
SCA组件可以通过传递业务对象来交换数据，如图8所示。
SCA components can exchange data by passing around business objects as shown in Figure 8.
如图4所示，元数据服务器管理名称空间部分，可以(为冗余和性能)进行重叠。
As shown in Figure 4, the metadata servers manage portions of the namespace and can overlap (for redundancy and also for performance).
实例元数据采用清单1所示的形式。
单击该徽章旁边的配置图标并为集群提供配置数据，如图8所示。
Click the configuration icon next to this badge and provide configuration data for the cluster as shown in Figure 8.
在字段中输入数据，如图2所示。
如图22所示，对输入数据应用NORMXML以删除xml空白(包括回车、换行、制表符和空格)。
As shown in Figure 22, the NORMXML is applied to the input data in order to remove any XML whitespace (including carriage returns, line feeds, TAB characters, and Spaces).
在这里您必须配置数据源以解决错误(如图30所示)，该错误与对数据库的连接有关(必须指定一种连接)。
At this point the data source must be configured to resolve the errors (shown in figure 30) concerning the connections to the database (must specify a connection).
清单2展示了该xrt脚本，用于从雇员数据库中检索数据，以及创建如清单3所示的XML中间数据。
Listing 2 shows the XRT script that is used to retrieve data from the Employee database and create the intermediate data XML shown in Listing 3.
这种首选“规范数据区域”如图3所示。
This preferred "canonical data zone" is also shown in Figure 3.
如图9所示，在数据层中有三个资源共享级别。
As shown in Figure 9, there are three levels of resource sharing in data tier.
应用推荐