下面的示例通过分析我们在前面小节中所捕获的糟糕查询，介绍访问计划的基础知识。
The example below introduces the access plan basics by analyzing the bad SQL statement we captured in the previous section.
记住，一旦应用程序被导出，您就必须手动签署和优化应用程序，跟前面介绍的那样。
Remember that once the application is exported, you have to manually sign and optimize the application, as covered previously.
这些过滤器和前面介绍的过滤器的工作原理是一样的，并且也是以“：”开头，表明它们是过滤器。
These filters work like the other filters introduced in this article and are preceded with a ":" character to denote they are a filter.
前面介绍的文件同步方法的主要问题是，它们会复制每个文件(和相关联的目录结构)。
The main problem with the previous alternatives for synchronizing files is that they copy every single file (and the associated directory structure).
现在要介绍一个简便的基准测试框架，这个框架解决了前面提到的许多问题。
Now I introduce a "ready to run" benchmarking framework that addresses many of these issues.
我们将对矩阵乘法的标准技术稍微进行一下修改，这样就可以使用前面介绍的算法了。
We'll make a slight change to the standard technique for multiplying matrices so that the previous algorithm can be applied here.
这方面的技术有两种，第一种是前面介绍的规则组和规则执行流。
There are two techniques for doing so, the first being the previously mentioned rule groups and rule-execution flows.
多对多关联的情况这里没有讨论，因为它的实现与我们前面介绍的大同小异。
The case of the many-to-many associations is not discussed here, as its implementation is quite similar to the relations we presented before.
前面介绍的 class属性可以满足这两个目的。
The class attribute that was introduced previously serves two purposes. It provides
让我们将它应用到前面介绍的FpML模式的生命周期示例。
Let's apply this to the lifecycle example for FpML schemas that was introduced earlier.
前面介绍的所有文件都存储在C： \MyTests \Datapool文件夹中。
All the files that were introduced earlier are stored in the c: \ MyTests \ Datapool folder.
为该应用程序创建用户界面要调用前面介绍过的三个文件。
Creating the user interface for this application involves all three of the previously introduced files.
使用前面介绍的方法准备一个包含10000条记录的输入数据集。
Prepare a set of input data with 10000 records using the previously described approach.
因此，在组织流程模型时，应始终保持结构清晰，同时从我们前面介绍的活动形式或网关形式中选择一种。
You should always organize process models in a structured manner and pick either an activity form or gateway form as we described in the previous section.
向导的第一个页面向您提供导入适配器的选项，我们已经在前面部分中介绍过。
The first page of the wizard gives you the choice of importing the resource adapter, as we described in the previous section.
本文还讨论了如何使用在前面几期文章中介绍的一些工具，以便对您的系统进行更改。
It also discusses how to use several of the tools illustrated in prior installments to make changes to your systems.
本教程依赖于本lpi考试系列前面的教程介绍的内容，所以您可能需要先参考针对考试101的教程。
This tutorial builds on content covered in previous tutorials in this LPI series, so you may want to first review the tutorials for exam 101.
本文剩下的部分将介绍现有的补偿框架并展示一个使用自定义解决方案的简单实现来阐释我前面介绍的概念。
The rest of this article describes an existing compensation framework and shows a simple implementation using a custom solution to illustrate the concepts I've described.
前面已经提供了几个简单的例子，现在详细介绍它的一些特定特性。
Having provided a couple of simple examples, now look in detail at some of its specific features.
前面介绍了所有必要概念，现在终于可以定义路由过程了。
Finally, now that we introduced all the required concepts, we can define the routing process.
还需要使用前面介绍的针对不同攻击类型的其他监视类型以及配置来确保与服务级协议的兼容性。
Other types of monitoring for the types of attacks mentioned above are also needed, as well as configurations to ensure compliance with service-level agreements.
使用前面介绍的技术，我们可以把这些单词移动到外部单词列表文本文件中，然后根据需要导入。
Using techniques covered earlier, we can move these words to an external word list text file and import them as we like.
出于量化用途，我使用前面研究中所介绍的两个有代表性的相同XML文档。
For quantification purposes, I work with the same two representative XML documents addressed in my earlier research.
在这个系列前面的文章中，我介绍了如何用代码度量客观地测试代码质量。
In previous articles in this series, I've shown you how to use code metrics to objectively measure code quality.
前面介绍的技术将有助于您选择新的堆参数。
The techniques described above will help to choose new heap parameters.
如前面所提到的，本文的目的是概要介绍自定义数据绑定以及其如何对您的应用程序有利。
As mentioned earlier, the purpose of this article was mostly to provide an overview of Custom Data Binding and how it can benefit your application.
正如前面介绍的一样，对标题进行排序和对艺术家进行排序的代码几乎是相同的。
As mentioned, the code for sorting by title and sorting by artist is nearly the same.
它们通常基于REST，因此只需一个简单的HTTP访问就可以检索数据，并使用前面介绍的结束来解析数据。
They are often REST-based and therefore require only a simple HTTP access to retrieve the data and parse it using the preceding techniques.
如前面部分“统一流程”中介绍的，您最初的评估应确定：哪些用户需要访问变更请求，如缺陷？
As described in the "a unified process" section earlier, your initial assessment should determine: Which users will need access to change requests such as defects?
前面已经简单地介绍了单例模式的实现方式，现在让我们进入主题：两个单例对象如何同时存在？
Now that we've looked briefly at implementation, let's turn to the heart of this article: how two singletons can exist simultaneously.
应用推荐