Deciding Between ODBC and JDBC Drivers

ODBC is an interface that does not depend on a specific programming language or a database system or an operating system. It can be used to write applications that can query data from any database, regardless of the environment it is running on or the type of DBMS it uses. Major advantage of having ODBC as a universal middleware between an application and a database is that every time the database specification changes, the software does not need to be updated. Only an update to the ODBC driver would be sufficient.

JDBC is a data API for the Java programming language. It is an interface that helps a client to access a database system, by providing methods to query and update data in the databases. JDBC is more suitable for object oriented databases

Java programmers can use JDBC-to-ODBC bridge to talk to any ODBC compliant database.

Deciding Between ODBC and JDBC Drivers :

Use native ODBC for:

• Fastest performance for data imports and exports
• Memory-intensive data imports and exports

Use JDBC for:

• Platform independence allowing you to work with any operating system (including Mac and Linux), driver version, or bitness (32-bit or 64-bit)
• Using Database Toolbox functions not supported by the native ODBC interface (such as runstoredprocedure)
• Working with complex or long data types (e.g., LONG, BLOB, text, etc.)

Tip:

• On Windows systems that support both ODBC and JDBC drivers, pure JDBC drivers and the native ODBC interface provide better connectivity and performance than the JDBC/ODBC bridge.

I think this might be helpful :- Choosing Between ODBC and JDBC Drivers