| description | ODBC Service Provider Interface (SPI) Reference |
|---|---|
| title | ODBC Service Provider Interface (SPI) Reference | Microsoft Docs |
| ms.custom | |
| ms.date | 01/19/2017 |
| ms.prod | sql |
| ms.prod_service | connectivity |
| ms.reviewer | |
| ms.technology | connectivity |
| ms.topic | reference |
| ms.assetid | cdeffb4a-f344-4abe-97f3-be2ede1c8e59 |
| author | David-Engel |
| ms.author | v-davidengel |
Traditionally, ODBC defined an application programming interface (API). The functions in the API can be called by applications and they should be implemented inside both the Driver Manager and the driver.
With the addition of the driver-aware connection pooling feature, ODBC introduces the service provider interface (SPI). The functions in the SPI are used for communication between the Driver Manager and driver. SPI functions are implemented by the driver; the Driver Manager does not expose SPI functions to applications. Applications should not call these functions directly.
Include sqlspi.h for ODBC driver development.
This section contains the following topics
Developing an ODBC Driver
Developing Connection-Pool Awareness in an ODBC Driver
Driver Manager Connection Pooling