Troubleshooting statement pooling
- Last Updated: August 28, 2020
- 1 minute read
- DataDirect Connectors
- JDBC
- Aha! 6.0
- Amazon Redshift 6.0
- Apache Cassandra 6.0
- Apache Hive 6.0
- Apache Spark SQL 6.0
- Atlassian Jira 6.0
- Autonomous REST Connector 6.0
- Cloudera Impala 5.1
- + 24
Similar to connection pooling, statement pooling provides performance gains for applications that execute the same SQL statements multiple times in the life of the application. The DataDirect Statement Pool Monitor provides the following functionality to help you troubleshoot problems that may occur with statement pooling:
- You can generate a statement pool export file that shows you all statements in the statement pool. Each statement pool entry in the file includes information about statement characteristics such as the SQL text used to generate the statement, statement type, result set type, and result set concurrency type.
- You can use the following methods of the
ExtStatementPoolMonitorMBeaninterface to return useful information to determine if your workload is using the statement pool effectively:- The
getHitCountmethod returns the hit count for the statement pool. The hit count should be high for good performance. - The
getMissCountmethod returns the miss count for the statement pool. The miss count should be low for good performance.
- The
See also
Refer to Statement Pool Monitor in the Progress DataDirect for JDBC Drivers Reference for further details.