Data sources connection pool and prepared statement cache.
数据源连接池和事先声明的高速缓存。
The data source statement cache size can be tuned using a few different methods.
可以使用一些不同的方法来调优数据库语句缓存大小。
The number of nontransactional statements that used the binary log statement cache.
使用二进制日志缓存文件的非事务语句数量。
However, you still need to be aware that the results depend on the current contents of the SQL statement cache.
不过，您仍然要记住，分析得到的结果仅取决于sql语句缓存的当前内容。
Data source statement cache size specifies the number of prepared JDBC statements that can be cached per connection.
数据源语句缓存大小指定每次连接可以缓存的经过准备的jdbc语句的数量。
Hint: you can also manually create an.sql file from your dynamic statement cache or using other preferred mechanisms.
提示：还可以从动态语句缓存或使用其他首选机制手动创建.sql文件。
The size you specify for the statement cache size should be relatively large. Typically this is in the range of 100-200.
您为语句缓存指定的大小应当相对较大，一般在100到200之间。
The size you specify for the statement cache size should be relatively large. Typically, this is in the range of 100-200.
您为语句缓存指定的大小应当相对较大，一般在100到200之间。
But we do have control on all kinds of cache, Data-distribution cache, Dictionary cache, SPL routine cache, and SQL statement cache.
但是，我们控制所有类型的缓存器，数据分布缓存器、字典缓存器、SPL例程缓存器和sql语句缓存器。
So when the same SQL statement is executed again, DB2 finds the previously created access plan in the statement cache and reuses the access plan.
因此，当同一个sql语句再次执行时，DB 2在语句缓存中找到此前创建的访问计划并重用它。
The DB2 optimizer stores the access plan created in the prepare phase in the SQL statement cache (also called package cache in DB2) for reuse purposes.
DB 2优化器将准备阶段中创建的访问计划存储在sql语句缓存(在DB 2中也称为包缓存)中以便重用。
If your JDBC program USES prepared statements and parameter markers, queries are processed faster if they are found in the database statement cache.
如果您的JDBC程序使用已经准备好的语句和参数标志，并且如果在数据库语句缓存中找到了它们的话，查询过程将处理地更快。
Looking back at the chart in Figure 11, before tuning the data source statement cache size, the number of statements discarded was over 1.7 million.
回过头来看图9中的表，在调优数据源语句缓存大小之前，被丢弃的语句的数量超过170万条。
Another option is to use Query Tuner to capture statements from the statement cache and to view the statement runtime information, as shown in Figure 7.
另一个选择是使用QueryTuner从状态缓存获取状态，并查看状态运行时信息，如图7所示。
As an alternative to an input file containing SQL statements, you can also have Design Advisor evaluate the contents of the database's SQL statement cache.
包含sql语句的输入文件有一个代替办法，即让Design Advisor计算数据库的sql语句缓存的内容。
The statement cache size can be configured by navigating to Resources => JDBC => Data sources => data_source => WebSphere Application Server data source properties.
要配置语句缓存大小，可以导航到Resources =>JDBC =>Datasources => data_source =>WebSphereApplicationServerdatasourceproperties。
The db2pd call gathers information about locks, transactions, applications, and the statement cache and stores this information in a text file for analysis purposes.
db 2 pd调用收集与锁定、事务、应用程序、语句缓存相关的信息，并将信息存储在一个文本文件中以供分析。
Therefore, when using the SQL statement cache as input, you should run the Design Advisor at different points throughout the day to evaluate a broader range of statements.
因此，当使用sql语句缓存作为输入时，应该在当天的不同时间点运行Design Advisor，以计算更大范围的sql语句。
In a J2SE environment, if the statement cache is too small or the batch size too large, you may receive SQL exceptions resulting from inconsistencies in the statement cache.
在一个J2SE环境中，如果语句缓存太小或批量太大，您可能会因语句缓存中的不一致性而收到SQL异常。
WebSphere Application Server provides such a pooling facility together with some additional performance helpers, like a statement cache for frequently executed SQL statements.
WebSphereApplicationServer使用一些额外的性能Helper提供这样的连接池机制，相当于频繁执行的 SQL 语句的语句缓存。
For example, an administrator can figure out what is the maximum number of database connections or optimum number for prepared statement cache size that should be used to handle a real world load.
例如，管理员可以决定数据库连接的最大数量，以及处理实际工作负荷应该所用的预备状态缓存空间的最优数量。
This cache remembers not only recently executed procedures. The cache also remembers previously executed statements, so that after the first compilation of the SQL statement.
该缓存不仅记住最近执行的过程，还记住了以前执行的语句。
When the statement is compiled, its access plan is stored in the package cache.
在编译语句时，语句的访问计划被存储在包缓存中。
If the same INSERT statement is executed repeatedly, its access plan will (usually) be found in the package cache and the compilation cost is avoided.
如果重复地执行相同的insert语句，则该语句的访问计划(通常)会进入到包缓存中，这样就免除了编译的开销。
Use of literals instead of variables or parameters is generally discouraged within SQL because it makes each statement unique, which drives down cache hit ratios.
一般情况下，不鼓励在SQL中使用字面值，而是主张使用变量或参数，因为字面值会使每个语句具有独特性，这会降低缓存的命中率。
Invoking the HISTORY command again shows that there are now five commands or statements in the cache, including the modified SELECT statement.
再次调用HISTORY命令来显示缓存中现在有5个命令，包括修改的SELECT语句。
If a guideline is updated, or deleted from the table, then it is necessary to refresh the cache by issuing the FLUSH OPTIMIZATION PROFILE cache statement, so it can be used.
如果从这个表中更新或删除一个指南，那么需要通过发出FLUSHOPTIMIZATIONPROFILEcache语句更新缓存，使之可以被使用。
To stop the Web server from caching your graphs, use the appropriate HTML META tags (for example, the 'no-cache' statement) in your scripts.
要想禁止Web服务器缓存图形，应该在脚本中使用适当的HTMLMETA标记(例如‘no -cache’语句)。
To stop the Web server from caching your graphs, use the appropriate HTML META tags (for example, the 'no-cache' statement) in your scripts.
要想禁止Web服务器缓存图形，应该在脚本中使用适当的HTMLMETA标记(例如‘no -cache’语句)。
应用推荐