

In such cases, we recommend that enterprises deploy an ODBC-JDBC bridge (a.k.a an ODBC wrapper) to make the JDBC compliant database look like an ODBC data source. Recreating an ODBC layer at the DB level or a JDBC support at the application may not be in your control or even cost-effective to build and maintain in the long run. That's one of the major reasons, you see a lot more applications support ODBC than JDBC.ĭevelopers often get into a dilemma when an application has been designed to consume ODBC drivers, whereas the database supports only JDBC. While JDBC was written for the Java environment, ODBC was designed to be language-agnostic. ODBC and JDBC are the most popular SQL standards adopted by developers to access data and run queries. Using these standards allows applications to send SQL statements to different data sources without having to code multiple times.
