| title | Interoperability | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 01/19/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | connectivity | ||
| ms.reviewer | |||
| ms.technology | connectivity | ||
| ms.topic | conceptual | ||
| helpviewer_keywords |
|
||
| ms.assetid | 43b7c849-9d59-4002-9977-9e2c8730b859 | ||
| author | David-Engel | ||
| ms.author | v-daenge |
Interoperability is the ability of a single application to operate with many different DBMSs. The need to write generic, interoperable applications was one of the major factors leading to the development of ODBC. However, interoperability is not a simple path followed from "not interoperable" to "completely interoperable." The path has many branches, and each requires trade-offs among features, speed, code complexity, and development time.
The process of writing an interoperable application follows several steps:
-
Deciding whether the application will use ODBC.
-
Choosing a level of interoperability and deciding which trade-offs are necessary to reach that level.
-
Writing interoperable code and testing it as fully as possible.
It should be noted that interoperability is primarily the domain of the application writer. Drivers are designed to work with a single DBMS and, by definition, are not interoperable. They play a role in interoperability by correctly implementing and exposing ODBC over a single DBMS.
This section contains the following topics.