SQLPrepare函数准备语句。
为了考虑这些变化，必须重新准备语句。
To account for these changes, the statement has to be re-prepared.
在客户机准备语句。
里面没有优势准备语句BEGIN（警告）。
There is no advantage to preparing statements inside BEGIN (with caveat below).
如果经常要准备语句，那么可以试着调低优化级别。
准备语句相比普通查询来说要快很多，当然跟使用的数据库有关系。
Prepared statements can be significantly faster than regular queries depending on the database being used.
注意1：如果数据库模式变化，声明需要必须重新准备语句。
Caveat 1: if the database schema changes, the statement will need to be re-prepared.
所有这些查询可以简化为一个参数化查询(也称为一个预准备语句)，如清单2所示。
All of these can be condensed into a single parameterized query (also known as a prepared statement), as shown in Listing 2.
还有其他优势准备语句以外的事务，例如，你可以使用它们在多个事务没有多次做准备。
There are other advantages to preparing statements outside transactions, e. g., you can use them in multiple transactions without preparing multiple times.
由于大部分数据库层支持能更好地处理该风险的准备语句，禁用该设置会再次消除这个烦人的性能问题。
Since most database layers support prepared statements that handle this risk much better, turning this off will again remove an annoying performance problem.
这个方面有两个主要职责：跟踪与创建和准备语句有关的信息，然后监视jdbc语句执行的性能统计值。
This aspect has two primary responsibilities: tracking information about creating and preparing statements and then monitoring performance statistics for executing JDBC statements.
另一方面，Net.Data仅支持立即执行，在这种情况下每次执行语句时都要准备语句。
Net. Data, on the other hand, supports only immediate execution, where the prepare is done each time a statement executes.
有一个小的优势在准备语句BEGIN因为事务将略小（与第二警告下面），从而允许更多的并发性。
There is a small advantage to preparing the statements outside the BEGIN since the transaction will be slightly smaller in time (with second caveat below), thereby permitting more concurrency.
这个建议可以匹配JDBC中12种不同的可以创建或准备语句的方式，而且是为了适应 JDBCAPI未来的扩展而设计的。
This matches the 12 different ways that a statement can be created or prepared in JDBC and is designed to adapt to future extensions to the JDBC API.
当使用静态SQL时，执行sql语句的准备步骤是在应用程序执行之前就进行的，因此可在运行时取得更好的性能。
With static SQL, the preparation steps for executing a SQL statement occur before the application is ever executed, thus offering the opportunity for better performance at runtime.
这样，当sql语句被多次执行时，准备阶段的时间和CPU资源将得以节约。
Thus time and CPU resources are saved in the prepare phase when SQL statements are executed many times.
执行所准备的语句。
解释完宏之后，连接将处于活动状态并准备执行sql语句(参见清单2)。
After the macro is interpreted, the connection is active and ready to execute SQL statements (see Listing 2).
常常希望只准备和编译UPDATE语句一次，然后在每次执行更新时传递一个新值。
Often you will want to prepare and compile the UPDATE statement only once, and then pass in a new value every time you execute the update.
如果没有启用MRF，准备fetch语句时将不包含行集定位。
If MRF is not enabled, FETCH statements are prepared without rowset positioning.
避免准备阶段在下面两种情况下最有用：一是sql语句被多次执行；二是准备阶段需要的时间占语句总执行时间的很大一部分。
Avoiding the prepare phase especially pays off if an SQL statement is executed many times and if the prepare phase makes up a significant portion of the statement's overall execution time.
关键是准备好的语句中的sql语句会引用游标的当前位置，所以您可以多次执行它，并更新不同的行。
The key is that the SQL statement in the prepared statement references the current position of the cursor, so you can execute it multiple times and update different rows.
应用程序准备(编译)好一条语句之后，可以修改语句对象——表、索引、统计信息。
After a statement has been prepared (compiled) by the application, the statement objects — tables, indexes, statistics — can be altered.
当执行预编译语句时，IDS检测底层对象的变化，必要时重新准备(重新编译)语句。
When you execute a prepared statement, IDS now detects changes to underlying objects and re-prepares (re-compiles) the statement if needed.
准备sql语句。
就是说如果sql语句要执行多次，开发人员应该只准备该语句一次，在以后的执行中重用准备好的语句。
It means that when an SQL statement is going to be executed more than once, the developer should prepare the statement just once and then reuse the prepared statements for consecutive executions.
然后在[2]中准备该语句。
准备和提交用于执行的语句。
比如说，olap4 j里创建连接、准备和执行语句的代码看起来和JDBC里的非常像。
For example, the code to create a connection, prepare and execute a statement looks very similar in olap4j and JDBC.
将重新准备fetch语句，并且不包含行集定位。
The fetch statement will be re-prepared without rowset positioning.
应用推荐