Enabling client optimization using the admin console.
使用管理控制台启用客户端优化。
Configuring client optimization in a clustered environment.
在集群环境中配置客户端优化。
Not all JDBC applications are good candidates for client optimization without modifications.
不是所有JDBC应用程序都能够在不经过修改的情况下进行客户机优化。
PureQuery client optimization, on the other hand, captures actively executing SQL statements.
另一方面，pureQuery客户端优化可以有效地捕获正在执行的sql语句。
PureQuery client optimization is being evaluated and implemented in more and more enterprises.
越来越多的企业正在评估和实施pureQuery客户端优化。
The Resources section contains a link to a tutorial that describes how to use client optimization.
参考资料部分包含一个教程链接，该教程介绍如何使用客户端优化流程。
For more details about the benefits of client optimization, see the Resources section of this article.
有关客户端优化的收益的更多信息，请参阅本文的参考资料部分。
As you may recall, the first article described how client optimization consists of the following main phases.
您可以回忆起，第一篇文章描述客户端优化包括如下主要阶段。
To tell Data Studio Developer that a particular project is eligible for client optimization, follow these steps
要告诉DataStudioDeveloper一个特定项目符合客户机优化条件，请执行下列步骤
When you enable client optimization in such an environment, it increases the possibility of resource contention.
在这种环境中启用客户端优化时，会增大资源争用发生的可能性。
You only need capture turned on when you are using the client optimization process described later in this article.
只有在使用客户端优化流程(本文后面会有介绍)时才需要打开捕捉模式。
Access to source code is not required for client optimization, but the steps in this tutorial assume you have such access.
客户机优化不需要访问源代码，但是本教程中的步骤假设您有那样的访问权。
You only need capture turned on when you are using the client optimization process that is described later in this article.
只有在使用客户端优化流程（本文后面会有介绍）时才需要打开捕捉模式。
pureQuery’s client optimization feature works by binding SQL that you have previously captured from the running application.
pureQuery 的客户机优化功能通过绑定以前从运行的应用程序捕获的SQL来进行工作。
You can get the benefits of static SQL with any existing DB2 JDBC applications, using pureQuery’s client optimization feature.
使用pureQuery 的客户机优化 特性，可以在任何现有的DB2JDBC应用程序上获得静态SQL 的益处。
You only need capture turned on when you are using the client optimization process that is described in the first article of this series.
您只有在使用本系列第一部分中描述的客户机优化流程时才需要开启采集功能。
Capture the SQL from the running application (or import captured SQL that you have previously captured) as described in client optimization.
像客户机优化中描述的那样从正在运行的应用程序捕获SQL(或者导入以前捕获的SQL)。
This feature is sometimes called client optimization because the process for enabling the static capability occurs at the JDBC client level.
这个特性有时候被称作客户机优化（client optimization），因为启用静态 SQL的过程是在JDBC 客户机这一级发生的。
Previously, performance metrics were only available for inline style applications and for those for which SQL was captured using client optimization.
此前，性能指标只适用内联风格应用程序，以及使用客户端优化为其捕获SQL的应用程序。
The following scenario is intended to help further describe how to configure and work with client optimization in clustered application server environments.
以下场景帮助更进一步描述如何在集群应用服务器环境中配置并使用客户端优化。
For optimizing existing applications using client optimization, you can generate multiple capture files to lock captured information during incremental capture.
要使用客户端优化优化现有应用程序，可以在递增式捕获过程中生成多个捕获文件来锁定捕获的信息。
Client optimization captures SQL from executing applications and enables administrators to bind the SQL to DB2 for static execution without changing a single line of application code.
客户端优化从执行中的应用程序捕捉SQL，使管理员能够将SQL绑定到DB 2实现静态执行，并且不需要更改应用程序的代码。
Client optimization captures SQL from executing applications and enables administrators to bind the SQL to DB2 for static execution without changing a single line of application code.
客户端优化从执行中的应用程序捕捉SQL，使管理员能够将SQL绑定到DB 2实现静态执行，并且不需要更改应用程序的代码。
应用推荐