• Statements allowed include INSERT, DELETE, and statements that return no data, such as CREATE TABLE.
• SELECT statements and row-producing procedures are not allowed in batched queries.
• If the DBMS does not support batch processing, the Ingres JDBC driver will detect it and automatically execute the statements individually.

• Statement must be a prepared dynamic statement
• Statement must be of the form “INSERT INTO……VALUES”
• Any values that are expected to change for each insert must be parameterized. As with all inserts, columns can be omitted if they are nullable or have default values (including identity columns).
• Parameters for the query must include only column values, other parameters (e.g. table name) are not allowed

• For local execution of non-dynamic statements and procedures, batch appears to have only a small performance improvement.
• For remote execution of non-dynamic statements, JDBC batch performance increases significantly up to a batch size of about 100 statements.
• For non-dynamic statements, there does not appear to be a significant improvement in performance for batch sizes over 100.
• Batch sizes of 100 and greater reduced communications round-trips to the point that little difference was seen between local and remote JDBC execution.
• For dynamic statements, performance just continues to increase as batch size increases due to the copy optimization.
• The copy-optimization for prepared statements is actually very detrimental for small batch sizes. Single statement execution ran at about a minute. Doing the same thing with a batch size of two statements increased the time to between 12 and 13 minutes! Execution times then dropped to 2 1/2 minutes at a batch size of 10 statements and only regained parity at a batch size approaching 100 statements. On the other hand, really large batches went screaming fast.

• Adding Support for the following JDBC 4.0 API features:
  • Automatic loading of java.sql.Driver
  • National Character Set Conversion Support
  • Enhances Support for BLOB and CLOB
  • Wrapper pattern
  • New Scalar Functions
  • SQLException enhancements
  • JDBC API changes to existing JDBC interfaces
  • SQL/XML and XML support
  • Connection Management

For more information on the Ingres support of the JDBC 4.0 API features, see JDBC 4.0 API Features Implemented.

A Community Preview of the Ingres JDBC Driver (iijdbc.jar) can be found at Community Preview Download Area.

• Boolean Data Type Support.

For more information regarding Ingres’s support of the Boolean Data Type, see Boolean Data Type Support.

A Community Preview of the Ingres JDBC Driver (iijdbc.jar) will be available in the future that exposes this support. An Ingres 10 DBMS and Data Access Server (DAS) are a must to exploit this feature.

• Batch Execution Support.

Batch processing (batch execution actually) is currently supported in the Ingres JDBC Driver but under the covers statements are not actually batched but instead are done as Singleton queries which undermine the performance improvement expected when batching queries. The feature was implemented in this manner due to the lack of support in the Ingres DBMS for batch processing. With Ingres 10, the DBMS will be adding capabilities to handle batch processing and the JDBC Driver will be modified to take advantage of the new Batch feature. This enhancement should significantly improve batch processing in the Ingres JDBC Driver.

For more information regarding Ingres’s support of Batch Execution in Ingres 10 and the JDBC Driver, see Batch Statement Execution Performance.

A Community Preview of the Ingres JDBC Driver (iijdbc.jar) will be available in the future that exposes this support. An Ingres 10 DBMS and Data Access Server (DAS) are a must to exploit this feature.