On JDBC data sources, the fetch size is hard-coded and cannot be modified - Support and Troubleshooting

On JDBC data sources, the fetch size is hard-coded and cannot be modified Issue  On JDBC data sources, the fetch size is hard-coded and cannot be modified

Problem Attempts are sometimes made to optimize the JDBC data source fetch size to meet different conditions.

Cause On JDBC data sources, the fetch size is hard-coded on the JDBC probe and cannot be modified.

Resolution Our version of this feature is the probe parameter jdbcprobe_result_set_rows, which modifies the MID server payload instead.

Probes interact with the MID Server via the ECC Queue, and therefore the response of a JDBC probe returns as an XML payload in an "input" ECC Queue record. By default, each response payload will contain up to 200 returned rows. This value can be modified by setting the probe parameter jdbcprobe_result_set_rows to the desired number.

Note : By default, each JDBC response payload will contain up to 200 returned rows.