Question

Suppose that you are writing an application which requires standardised, high volume accesses to a back-end SQL database via the JDBC API. You may assume that the tasks involve a mix of simple queries – with variations in the query parameters – and a number of more complex DB operations. The best approach for these high-volume queries is most likely to involve:

(a) use of the JDBC:ODBC bridge and carefully constructed groups of Statement objects.

(b) use of the JDBC:ODBC bridge, Statement objects and stored procedures.

(c) a vendor-specific Java DB driver and carefully constructed groups of Statement objects.

(d) a vendor-specific Java DB driver and wide use of PreparedStatement objects.

(e) a vendor-specific Java DB driver and use of PreparedStatements and stored procedures.

Answer 1

The Best approach for these HIgh Volume Queries is Most Likely to Involve :

Option C

A vendor - Specific Java Database driver and carefully constructed group groups of statements objects.

That means

If we are writing an application that requires the standardizes and high volume access to a back-end SQL database via the JDBC API.

We need to assume the tasks that involve a mix of simple queries that provide the variations in the Query parameters and a number of more complex DB operations.

Here is the Best approach that is Very high volume queries that uses a Vendor specific Java Database driver and carefully constructed groups of statements objects