Depending upon the relational database you are using, you can improve communication performance by adding the command caching, /CAn, parameter to the SQL task. Command caching allows each command that is retrieved and executed to be stored in memory. Performance improves the next time a command is to be executed. Because the command is in memory, it does not have to be retrieved again.
A command can be executed without actually having to access the database that stores the command. Thus, the connection to the command table database can be broken and the task can still use the command.
Using command caching, it is possible to read a command from one database, execute it in another database specified in the SQL Trigger block, and save the handle. Refer to the Using Multiple Relational Database Support section for more information on using multiple relational databases with iFIX ODBC.
