After you capture SQL statements in a pureQueryXML file, you might discover that one or more statements do not perform as well as your application requires. However, because you discover this fact late in your development cycle, modifying the application might not be possible. You can edit the pureQueryXML file by adding an alternative SQL statement for each SQL statement that is underperforming. When you run your application, pureQuery uses the alternative SQL statements, instead of the SQL statements that you originally captured.
For example, an SQL statement might start to perform poorly after you collect statistics for a table. If this problem occurs on a production system, a database administrator might need to reverse the change to the table's statistics or request a change to the SQL in the application. With pureQuery, the database administrator can forego these options and instead add an alternative SQL statement to the pureQueryXML file in which the underperforming statement appears.
To use these alternative statements, you must set the enableDynamicSQLReplacement property to TRUE when you run your application.
You can add an alternative statement for any SQL statement except one of either of these two types:
To add alternative statements or to edit alternative statements: