The encyclopedia · Software & IT · Technical decision · 1992–1995
ODBC gave applications one interface to any database and became the standard
Microsoft and the SQL Access Group released ODBC in September 1992; apps call one API, drivers translate to each database, and it still ships in Windows.
Microsoft · SQL Access Group
The solution
In the early 1990s every database vendor shipped its own programming interface, so an application written for one DBMS could not talk to another without being rewritten. The SQL Access Group — a collection of software companies that included Microsoft — formed to standardize the use of databases by applications.
The answer was ODBC (Open Database Connectivity), a call-level interface released in September 1992. Applications call a single set of SQL functions; a driver implements those functions for a specific DBMS, working much like a printer driver so one application can reach many data sources through one central interface.
The design won because it moved the hard part to the driver. Microsoft published the interface and made driver development the path to every database on Windows; version 2.0 followed in 1994 and 3.0 in 1995, and the API became a fixture of enterprise data access.
Why it worked
- One generic API replaced an N×M mess of vendor-specific interfaces
- The driver model let every DBMS vendor join by writing one adapter
- Shipping inside Windows gave ODBC instant distribution to developers
- Later alignment with ISO SQL/CLI kept it relevant instead of proprietary
What can be applied
When every supplier has its own interface, the fix is not more adapters but one stable interface every supplier can implement — the layer, not the endpoints, becomes the standard.
Aftermath
ODBC 3.0, released the same year as Windows 95, is still the base of most Linux drivers and many applications. In 2011 Microsoft announced it was focusing native client data access on ODBC, and modern Windows and SQL Server connectivity still documents the ODBC interface first.
Sources
spotted an error? The archive wants to know.