| title | Communicating with SQL Server (ODBC) | Microsoft Docs | |||
|---|---|---|---|---|
| ms.custom | ||||
| ms.date | 03/16/2017 | |||
| ms.prod | sql-server-2016 | |||
| ms.reviewer | ||||
| ms.suite | ||||
| ms.technology |
|
|||
| ms.tgt_pltfrm | ||||
| ms.topic | reference | |||
| helpviewer_keywords |
|
|||
| ms.assetid | cca3dcf0-2a7e-465a-84de-7ce055360eb6 | |||
| caps.latest.revision | 34 | |||
| author | JennieHubbard | |||
| ms.author | jhubbard | |||
| manager | jhubbard |
[!INCLUDESNAC_Deprecated]
For an ODBC application to communicate with an instance of [!INCLUDEmsCoName] [!INCLUDEssNoVersion], it must allocate environment and connection handles and connect to the data source. After a connection is established, the application can send queries to the server and process any result sets. When the application has finished using the data source, it disconnects from the data source and frees the connection handle. When the application has freed all its connection handles, it frees the environment handle.
An application can connect to any number of data sources. The application can use a combination of drivers and data sources, the same driver and a combination of data sources, or even the same driver and multiple connections to the same data source.
You can download [!INCLUDEssNoVersion] Native Client ODBC samples from the SQL Server Downloads page on MSDN.