The prepareAllSQLStatements build descriptor option controls the kind of JDBC object that EGL uses to run an SQL statement.
The object that EGL uses depends on a number of factors. EGL always generates PreparedStatements for DB2® and Derby. In most cases, PreparedStatements are more efficient because they can be cached by the J2EE server and reused, but in other than J2EE environments, PreparedStatements can degrade performance. For this reason, the decision to force the use of PreparedStatements is left as an option. The default value is NO, which means that EGL makes the choice of which object to use.
Try both settings for your applications and see which gives you better performance.
You might also be able to improve performance by caching PreparedStatements. For details, see “cachePreparedStatements.”
The prepareAllSQLStatements build descriptor option has the following values: