Addressing Burdens of Open Database Connectivity Standards on the Users

Application Program Interface (API) is a general term used to identify a set of high-level routines that can be used by an application program to access and keep track of lower-level services in Operating System (OS), Database Management System (DBMS), graphics system, or a network. Open Database Connectivity (ODBC) is an API, which initially is defined by the SQL Access Group (SAG) to provide access to different database systems from MS windows platform. The ODBC not only becomes widely accepted standard to database tier-connectivity but also enables database's application to access a heterogeneous data on multi-tries environment and able to connect many registered database engines and simultaneously issuing SQL commands. As we have started studying for ODBC impact upon database since 2003 when ODBC was DBMS-dependent constituent; meanwhile ODBC were being in its preliminary developing stages. This paper investigates the recent ODBC capabilities and issues after a radical change in ODBC component and functionality and becoming DBMS-independent constituent using the practical way of benchmark between Oracle vs. MS SQL.This work is subdivided into section 1 which prologues database connectivity. Section 2 is this research problem. Section 3 emphasizes ODBC-burden's interoperable parties. Section 4 addresses ODBC-burden's victim domain. Section 5 briefly presents benchmark experiment results for this research purposes and verifies the results versus Ken North's results. Section 6 exposes ODBC-burden's sources. Section7 introduces ODBC-burden's key success factors. Conclusion is summarized in section 8.