ODBC Myths Dispelled
Open Database Connectivity Without Compromise !

The architecture of the OpenLink ODBC (MT) Driver, dispels two very deep rooted misconceptions in the Client-Server segment of the Information Technology industry ;

• ODBC is Slow
• Database Vendors are the best, or only source of ODBC Drivers.

ODBC is Slow

The first generation of ODBC Drivers have typically emerged from a single tier of development. This development has involved using Embedded SQL products, or Call Level Interface products, provided by numerous database vendors. These products are provided by database vendors to facilitate the development of client applications that communicate with their specific database engines via transparent database server application programming interface calls. Increasingly a lot of these products are now available under Microsoft Windows, and are the prime building blocks of all ODBC Drivers.

The problem with this approach is that applications/drivers built in this manner are totally dependent on additional communications products provided by these same database vendors, to enable your applications/drivers communicate with remote databases. Most of database vendor provided communications products are not optimized for ODBC (as most of them have been around for years prior to the arrival of ODBC), and in some cases do not implement a true Client-Server communications protocol (this is different to the underlying transport protocol (TCP/IP, SPX/IPX etc.) ). The communications technology in all situations is database specific, even though a few vendors provide gateways to other database engines. Add windows programming and emerging standards such as WINSOCK (which includes extensions, that enable asynchronous network communications), to this picture, and you are left with an unbelievable recipe for pandemonium.

This recipe for pandemonium has already been experienced by the numerous ODBC early adapters, and has been one of the prime reasons why the concept underlying ODBC appeared to be flawed as it apparently compromised performance.

Since the announcement and delivery of OpenLink ODBC (MT) Drivers this myth is increasingly being put to rest. As OpenLink's concept of equipping ODBC Drivers with a Database Independent Communications Layer has already started to re-enforce the viability of the underlying concepts on which the ODBC standard has been founded.

Database Vendors are the best source of ODBC Drivers

ODBC Drivers do not have to be purchased from database vendors only, neither are they the best source of ODBC Drivers, bearing in mind ODBC has accelerated the process of database commoditisation. Databases systems are fast becoming commodity items just like computer hardware.

ODBC Drivers supplied by a database vendor will obviously only work with communications software also provided by that database vendor. If there are any problems with the communications layer, or you have numerous database systems from different database vendors in your organization you will feel the pain both in terms of ODBC unsuitability and cost. The OpenLink ODBC (MT) Driver is licensed on a concurrent usage basis only, irrespective of the number of databases that you will be connecting to, or the number of PCs connecting to databases in your organizations network.

The OpenLink ODBC (MT) Driver does not require the purchase of additional communications software just because you need to access another database type within your organization via ODBC compliant applications.

Table Of Contents | Next | Previous