choose between odbc and jdbc drivers -凯发k8网页登录

defining database drivers

database vendors, such as microsoft^® and oracle^®, implement their database systems using technologies that vary depending on customer needs, market demands, and other factors. software applications written in popular programming languages, such as c, c , and java^®, need a way to communicate with these databases. open database connectivity (odbc) and java database connectivity (jdbc) are standards for drivers that enable programmers to write database-agnostic software applications. odbc and jdbc provide a set of rules recommended for efficient communication with a database. the database vendor is responsible for implementing and providing drivers that follow these rules.

deciding between odbc and jdbc drivers

odbc is a standard microsoft windows^® interface that enables communication between database management systems and applications typically written in c or c .

jdbc is a standard interface that enables communication between database management systems and applications written in oracle java.

database toolbox™ has a c library that connects natively to an odbc driver. database toolbox has a java library that connects directly to a pure jdbc driver.

depending on your environment and what you want to accomplish, decide whether using an odbc driver or a jdbc driver meets your needs.

use native odbc for:

use jdbc for:

the only limitation for these drivers is memory performance. matlab^® memory restricts the native odbc driver. however, both matlab and jvm™ heap memory restrict the jdbc driver.