Browse Prior Art Database

Universal JDBC Database Driver to communicate with databases from different vendors Disclosure Number: IPCOM000243752D
Publication Date: 2015-Oct-16
Document File: 2 page(s) / 52K

Publishing Venue

The Prior Art Database


This article proposes the concept of a client side software program, called the Universal Driver - which allows client applications to communicate with databases from different vendors by dowloading vendor specific drivers under the covers. Vendor specific driver need not be pre-installed in the client workstations as they are done today.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Universal JDBC Database Driver to communicate with databases from different vendors

Database vendors supply their own Database drivers to allow connectivity, reads and writes to their database server. These drivers need to be pre-installed before any distributed communication to the database server is possible. There are several issues with the current approach of dedicated database drivers for different vendors -

1) A customer environment is typically heterogeneous where many databases are used. As an example, a large banking customer has DB2 for z/OS, DB2 for LUW, Oracle and mySQL to service different applications. This means that multiple database drivers need to be installed and managed over their lifetime.

2) Release of drivers across vendors is not coordinated. Each vendor comes out with updated drivers at different times and their recommendations on the level of driver that customers should run with for a particular level of database server keeps changing. Customer has to keep track of all updates, and install the new driver on all their affected client workstations (which can run into thousands in a large customer shop). Installation process needs to be repeated for each new driver that is released by different vendors out of the many drivers a customer may have.

3) Due to the overheads associated with keeping track of driver installs, many customers run with older levels of drivers which may not be recommended for the level of database server they are running with. Out of date drivers lead to problems and outages that could have been avoided in the first place.

Our proposal is to build a vendor neutral Universal JDBC Database Driver. This Universal driver is installed on the client workstations and helps in communication with relational databases offered by different vendors in the following way :

1) Only Universal Driver needs to be pre-installed in customer's clients (workstations a...