On JDBC data sources, the fetch size is hard-coded and cannot be modifiedDescription<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; } .hd3{ color: #7a7a7a; font-weight:; font-size:16 px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14 px; text-decoration:; } body.c5 {height: 100%;} td.c4 {vertical-align: middle; text-align: left;} td.c3 {width: 50; vertical-align: middle; text-align: center;} img.c2 {align: baseline;} hr.c1 {border-top-width: 1px; border-top-style: solid; border-top-color: #cccccc;} --> On JDBC data sources, the fetch size is hard-coded and cannot be modified ProblemAttempts are sometimes made to optimize the JDBC data source fetch size to meet different conditions. CauseOn 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.